+ <li>
+ dwm has no 9P support, no menu, no editable tagbars,
+ no shell-based configuration and remote control and comes without
+ any additional tools like printing the selection or warping the
+ mouse.
+ </li>
+ <li>
+ dwm is only a single binary, it's source code is intended to never
+ exceed 2000 SLOC.
+ </li>
+ <li>
+ dwm is customized through editing its source code, that makes it
+ extremely fast and secure - it does not process any input data which
+ hasn't been known at compile time, except window title names.
+ </li>
+ <li>
+ dwm is based on tagging and dynamic window management (however simpler
+ than wmii or larswm).
+ </li>
+ <li>
+ dwm don't distinguishes between layers, there is no floating or
+ managed layer. Wether the clients of currently selected tag are
+ managed or not, you can re-arrange all clients on the fly. Popup-
+ and fixed-size windows are treated unmanaged.
+ </li>
+ <li>
+ dwm uses 1-pixel borders to provide the maximum of screen real
+ estate to clients. Small titlebars are only drawn in front of unfocused
+ clients.
+ </li>
+ <li>
+ dwm reads from <b>stdin</b> to print arbitrary status text (like the
+ date, load, battery charge). That's much simpler than larsremote,
+ wmiir and what not...
+ </li>
+ <li>
+ garbeam <b>does not</b> want any feedback to dwm. If you ask for support,
+ feature requests, or if you report bugs, they will be <b>ignored</b>
+ with a high chance. dwm is only intended to fit garbeams needs.
+ However you are free to download and distribute/relicense it, with the
+ conditions of the <a href="http://wmii.de/cgi-bin/hgwebdir.cgi/dwm?f=f10eb1139362;file=LICENSE;style=raw">MIT/X Consortium license</a>.
+ </li>