While I'm interested in being able to fork the programs I use, and most likely upstreaming the changes, I'm not interested in having to do so to configure them. Configuration files are not stupid and are there for a reason.
There's a philosophy behind that decision, which you (and, in part, I) can disagree with. But they do have their reasons to prefer avoiding configuration files.
Of course I childishly played with the name (but that's their fault picking this name :-)). And of course one can disagree.
I like their goal of minimalism and simplicity. I disagree that developer's simplicity should be at the expense of the user's convenience. Computers are already incredibly complex things, and are here to automate things and ease our lives as users. Hopefully a program is written once and used many times, so usage should be optimized, even if it makes the developer's lives a bit harder (I would say interesting :-)). Making software lean and lightweight is part of it (and that's where I agree with suckless), we owe this to our users instead of forcing them to experience slowness and to upgrade their hardware often. Of course that's my view.
(I'm a dev)
It also entirely defeats the ostensible purpose of making "non-bloated" software because it doesn't get much more bloated than having to recompile an entire program every time you want to make a trivial change that could just be read from a file. You've now made having the entire compiler toolchain installed a requirement if someone wants to change a font.
It's the equivalent of burning your house down and building a new one because you want to change a poster on the wall. Suckless software is just an exercise in contrarianism.
In the past I've seen links here on HN where certain OSS authors were pressured into helping, fixing, adding features by users who 'demanded' it and the authors were feeling very bad about all this. It wasn't just one post.