Comments by "Anony Mousse" (@anon_y_mousse) on "Dwm Is a GREAT Window Manager (After It's Patched!)" video.

Truthfully, as a programmer, I agree even if we're not talking end users. It's super easy to just download or write a configuration file module and use that to read settings. All you need then is a button or shortcut key somewhere to refresh the config and done. It's a lot faster and doesn't require you to reboot/relog or whatever other hoops you'd need on top of recompiling the source to do something as simple as change a shortcut key. And if you have conflicts, you'd have to add "debugging" on top of that.
1
@herbertwestiron I can't read your whole comment because apparently it got censored, but I did see the word "untruthful" and I'd like to know how you think that.
1
@herbertwestiron That's down to the individual program(s) in use. As a KDE user, changing shortcut keys requires no restart, no (logout then login) and nothing more than either hitting the Apply or Ok button. This is the correct way to structure a program, config file changes shouldn't require more. If I have to compile a program and still relog/restart/whatever to change a simple shortcut key, then that's a bad way to structure a program. It's not misleading anyone to suggest that they should follow suit with developers that write better programs. Even if it is bloated, most people have the resources for that better functionality.
1
@herbertwestiron I'm not saying such people are wrong. I'm saying the developers are wrong. This can be handled exactly the same as KDE does it without taking up 700mb. It's just a matter of having a good programmer writing the code.
1
@herbertwestiron Could incorporate a default config into the source that gets generated upon first run. You could modify that to keep it portable as one archive, since it has multiple files to compile you really can't make the argument that it's one thing to drop into place. Even with binaries you still need multiple programs to have a usable OS, and if it had a default config, setup by you the user, it would still work just the same for you and allow others more utility. Just saying, there's more than one solution.
1
@herbertwestiron Like I said and you disregarded, the default config could still be in the source directly and no need to copy it as a separate file or figure out where it needs to be placed, for that matter, another methodology would be to have a separate config file possible by merely checking for its presence and using it if there or built-in default if not. Although, there's an idea, I just might fork the project and add all of these features because it'd be nice to have something that's so light but does more of what I want. Its super tiny size makes it an ideal starting point.
1
@herbertwestiron Are you a developer of any kind? Having the default config, which could easily be changed and incorporated into the source code to regenerate or maybe leave internal is a super easy thing to do. I've done it myself on multiple projects, and it's a lot easier to do now days with the syntax modern C has in object initialization.
1
@theodorealenas3171 Weird, I just looked and there is no sw in dmenu, but there is in dwm. It's also only initialized in one place and updated in another. Two places where it's set/modified. C is case sensitive, so finding a variable is pretty easy, just do a search for \<var\> where var is the name of said variable. (Obviously remove the backslashes if you're using proper PCRE.)
1
@theodorealenas3171 I downloaded a copy the other day and was considering testing it out. Going to read all of its code eventually. Assuming I don't die of a heart attack before I finish moving.
1