Indeed parsing a configuration file, or even running a scripting language like Lua is unnoticably fast, under 1 ms.
we need a few more "we did xyz and foo because it has these advantages but didn't do abc because it really doesn't work well with foo and you can patch in foobar if you want foo to go faster but don't need to do sneed with it" in this world instead of "xyz and foo are the best ever"
"but using a whole open read close call to read it is le bad and then we would need to write more heccin lines of coooode aaaa" - sperg
in their defense you can fuck up a text configuration file bad enough that a well-written program will say "dude what the fuck are you doing"
Sadly, I have spent significantly more time debugging configs because some shitware refused to report errors properly, than recompiling with what I needed.
how about it having a very specific location it looks for configs but the config doesn't exist by default and there is so little documentation that you don't know where to put it
This, with its twin brother: creating the config files upon start up, right at your fucking home directory.
oh yes i have long given up on the war on 19 page long home directory listing
You know, it should be impossible for a file to look smug, but the second that little shit gets into the version control, I swear its doing it.
https://git.suckless.org/dwm/file/config.def.h.html -- config.h just defines a few arrays and structs. No string mangling at all.
C-language config also works as a barrier-to-entry. Jeets and Low-IQs get filtered very early.
Some of the platforms where I run DWM take several seconds to execute something "trivial" like "yt-dlp --help". This is due to the whole tree of python dependencies the interpreter has to walk through. When running Linux off of a USB, too, you can run into this. Slow storage does weird things.
Including a config file in the executable is awesome. Some programs embed a zip archive in the executable for auxiliary files, for example the LÖVE game engine.
The suckless devs are really smart people and know how to make solid, fast software but take their autistic purism too far IMO. I use st because it's the best X11 terminal (for me) that I know of. Not because of their configuration or extension (patches) method, but despite.
And yes that result is a good thing, however it might also be a sign that the solution is overly complex or unfriendly, which I believe it is.
Definitely, more people should host their own git. It's really easy as you can just use any static web server.
With every update it gets more and more jeetslop. It's retarded that github, proprietary shitware took off as "the git host" to begin with
Luckily, on Linux at least, you have options. "strings" on the binary, grep for '/' to reduce the output and look for likely candidates. If that doesn't work, there's always "strace" and look for the stat and open calls to see what the hell it's doing.
given how often you restart a window manager it probably doesn't really matter whether the config is baked into the application or not
that is unfortunately a thing but there is also the magic of linux io caching and that it's not too hard to get your hands on a computer that isn't crippled, because even most low-end bullshit these days tend to come with ssds
they have a golden hammer and it makes no sense (experts crave internally simple software? what? explain emacs)
my main problem is that i don't want to maintain a whole extra step to use a package (since i am used to the typical workflow, which is to obtain THE binary from my package manager of choice and then use it)
once upon a time it was sourceforge
also rtfs
With lisp nothing with it's little retarded brother elisp a lot such a lack of proper concurrency
lisp is one of the most beautiful language families in the world but some of its progeny are ancient and retarded and make a lot of weird assumptions
elisp's lack of concurrency is one thing but then there's also the fact that it doesn't do lexically bound variables by default and tons of other weird cruft
You need to check the result of an allocation to satisfy basic programming competency. That's a minimum expectation outside of standards compliance.
yes rust shill i know if i induce ub i am a bad programmer but thankfully i can have defined behavior if i ensure my program operates according to the assumptions of the standard, such as by not dereferencing a null pointer returned by
mallocmalloc in such a way that it aborts your program if it returns a null