I think dwm has the best approach to configuration: change the program and recompile.
This works for dwm because it compiles in two seconds and has minimal dependencies. I don’t know about hyprland.
I think dwm has the best approach to configuration: change the program and recompile.
This works for dwm because it compiles in two seconds and has minimal dependencies. I don’t know about hyprland.
Requiring a C compiler, source code and header files to change your keybindings is just a different kind of bloat, and nothing can change my mind.
Then I won’t try! And I understand your opinion. But like everyone else I have many programs using many different configuration syntaxes, some using more than one file, some files in nonstandard locations, and some combining configuration from one or more files in my user directory with others somewhere in /etc or who knows where. I find the dwm approach refreshing.
Pontification added later: And it has a beneficial side-effect. I’m not much of a C programmer these days (if I ever was), but I found I was able to understand the dwm code well enough to make some small changes in behavior. So the dwm approach encouraged me to go beyond changing definitions in the headers. (This is aside from 3rd party patches. I was even able to contribute one of those.) This is really in the spirit of free software.