On Sun, 2013-09-01 at 19:22 +0100, Carlos R. Mafra wrote: > When was the last time you wanted to --replace a window manager? >
Speaking of me: did it every time I was interested in a window manager development enough to run a bleeding edge version of it, to compare behaviours when anything went wrong: --replace it with the version I have in my system, then --replace with dev version again. Of course this is not possible with WindowMaker. Because its developers are so tough that they use temporal relastatics, so that switching between window managers to find a bad commit when bisecting takes zero time. The rest of us, unfortunately, finds it easier to find a bug in a window manager that can be --replaced. Here, the bloat is not a valid argument. Compositing and wobbly windows ARE bloat. Making the dock look like and animate like OS X IS bloat. Making windows themeable, metacity-style, IS bloat. Adding support for a command line switch that every other window manager alive supports, which would immensely simplify debugging and work on integration of WMaker into other DEs (which WM was once famous for but no longer is), IS NOT. How I know it isn't? Because WindowMaker carries a whole bloody undermaintained widget toolkit usable by nothing but itself, and that for some obscure reason is "not bloat". > In my case, I _never_ did this. I don't see the point, sorry. There are people who do see the point. One of them even cared enough to make a patch. Do you think he's got no better use for his time? Sorry for being blunt, but the concept of what is "bloat" here just hit me on the nerves. But I agree, that if there are patches to make XRandR support unbroken, those would be more important... Unless, of course, XRandR is bloat. -- To unsubscribe, send mail to wmaker-dev-unsubscr...@lists.windowmaker.org.
