Skip to main content

I'm so SICK of stuff not working. When I dreamed of being a programmer as a child, it never occurred to me that writing the actual code is going to be the easiest, least time-consuming, and generally fun part. Now it feels like I am betrayed by my dream. Because whatever I'm trying to do, I keep running into weird issues, not covered by documentation, not answered on StackOverflow, not heard of by professionals I talk with. It's just too much of a headache to keep trying to fix what other people broke. All fun and games when you're just screwing around, exploring cool things you like. But say you need to get the job done? Nah.
frustration (x) programming (x) software (x)

My biggest wish right now is for all the bugs I encounter to be in MY OWN code. So at least it's mine and I can fix it myself.

Funnily enough, the exact cause of my little tantrum here was my very recent experience with Gradle-based stuff and npm. Not only it's binary blobs, it just sucks.

Any time I see a package manager that defaults to binary dependencies, it raises some huge red flags for me. I dunno what to do about it though. You can't just rewrite everything all by yourself.

Right, I'm still recovering after reading a whole bunch of Stallman's articles. No idea what to do here, guess the only reasonable way is to stay as clean as possible but not more than that.

What I do is try to educate others on what a scam "compilation not guaranteed" is. That doesn't help me program better, but maybe it'd help some third party prioritize having working compliation instructions, so I would have one less mess to deal with. It's honestly not very effective though, so I dunno.

My current approach is to install a minimalist OS like OpenBSD, install as few packages as I can and compile the rest myself (while still trying to use as little as possible). Opensource fans like to talk about how everything is open to inspection/modification, 'many eyes', etc while in reality lots of critical software is effectively closed source because it requires too much effort to analyze or modify in a nontrivial way and there's no infrastructure to make it easier. In the future I plan to write a very small highly integrated OS for a small number of SBC platforms.
It’s just too much of a headache to keep trying to fix what other people broke.
Not least because they just keep breaking it and if you criticize them they'll tell you that patches are welcome, you ungrateful fuck. There's an article documenting problems with the FreeBSD developer culture, I showed it to a FreeBSD fan a couple of years ago (in I2P, so he was at least somewhat interested in security), he just shrugged i... show more

This website uses cookies to recognize revisiting and logged in users. You accept the usage of these cookies by continue browsing this website.