4 ms·

Now this is why I don't use AwesomeWM, config breaks every-damn-time.

• stiff 14y ago
  I spent 30 minutes trying to convert my config from 3.4 to 3.5 and then gave up and came back to dwm, meanwhile it gained better support for multiple monitors, the only reason I used awesome in the first place...
• nemo1618 14y ago
  yeah, it's been a nightmare converting all my old widgets... but in a way, I'm glad that projects like AwesomeWM have the freedom to break everyone's configs if it means newer coding standards. The alternative -- retaining support for all previous versions, at the expense of bloat -- is much less preferable.
  • mercurial 14y ago
    It's debatable. In the real world, good APIs which evolve deprecate their obsolete parts instead of outright removing them. If that's too much bother, maybe it gets to show that APIs-as-configuration-files are a bad idea, especially with dynamic languages.
    • pyre 14y ago
      Awesome is the only API-as-configuration-file that I know of which consistently breaks the API between point releases.