26 As founder and main developer of wmii I came to the conclusion that |
26 As founder and main developer of wmii I came to the conclusion that |
27 wmii is too clunky for my needs. I don't need so many funky features |
27 wmii is too clunky for my needs. I don't need so many funky features |
28 and all this hype about remote control through a 9P service, I only |
28 and all this hype about remote control through a 9P service, I only |
29 want to manage my windows in a simple, but dynamic way. wmii never got |
29 want to manage my windows in a simple, but dynamic way. wmii never got |
30 finished because I listened to users, who proposed arbitrary ideas I |
30 finished because I listened to users, who proposed arbitrary ideas I |
31 considered useful. This resulted in an extreme <a href="http://www.jwz.org/doc/cadt.html">CADT model</a> |
31 considered useful. This resulted in an extreme <a href="http://www.jwz.org/doc/cadt.html">CADT</a> |
32 of developmentwhich was basically my mistake. Thus the philosophy of |
32 development model, which was a mistake. Thus the philosophy of |
33 dwm is to fit my needs. That's it. |
33 dwm is simply <i>to fit my needs</i> (maybe yours as well). That's it. |
34 </p> |
34 </p> |
35 <h3>Differences to wmii</h3 |
35 <h3>Differences to wmii</h3 |
36 <p> |
36 <p> |
37 In contrast to wmii, dwm is only a window manager, and nothing else. |
37 In contrast to wmii, dwm is only a window manager, and nothing else. |
38 Hence, it is much smaller, faster and simpler. |
38 Hence, it is much smaller, faster and simpler. |