2 ms·
A yaml config would still be weak (this has been discussed before: http://www.haskell.org/pipermail/xmonad/2009-February/007239.html http://www.haskell.org/pipe
by gwern 15y ago
A yaml config would still be weak (this has been discussed before: http://www.haskell.org/pipermail/xmonad/2009-February/007239.html http://www.haskell.org/pipermail/xmonad/2009-February/007239... )
But the nice thing about starting with a full language using the normal API is that you can always water it down to get something less powerful and easier to use, and this has been done with Xmonad before, as 'xmonad-light'. See https://braincrater.wordpress.com/2008/08/28/announcing-xmonad-light/ https://braincrater.wordpress.com/2008/08/28/announcing-xmon... http://www.haskell.org/pipermail/xmonad/2008-August/006211.html http://www.haskell.org/pipermail/xmonad/2008-August/006211.h...
xmonad-light has no users and may be bitrotten by now, which shows how much it appealed to Xmonad users.
- pyre 15y agoXMonad users by definition already know at least a minimal amount of how to create their XMonad config file. That's like saying: "We created a Linux distro for the masses and it didn't appeal to power users, therefore nobody wants it." You're also dismissing the possibility that is just sucked, and was not an improvement in configuration interface.