OpenBSD

The world doesn't live off jam and fancy perfumes - it lives off bread and meat and potatoes. Nothing changes. All the big fancy stuff is sloppy stuff that crashes. I don't need dancing baloney - I need stuff that works. That's not as pretty, and just as hard. Low code quality keeps haunting our entire industry. That, and sloppy programmers who don't understand the frameworks they work within. They're like plumbers high on glue. It's terrible, everyone is using it, and they don't realize how bad it is. And the Linux people will just stick with it and add to it rather than stepping back and saying, 'This is garbage and we should fix it. I say things as they are. Slackers are called slackers, people who can't read manual pages are called losers, and in general, calling things what they are results in developers wasting less time. In the Unix system view, anything which needs to talk to raw devices INSTEAD OF THE KERNEL DOING SO is broken. There are no apologies to be made. Period. If you want X to talk to IO devices, what next? ls?

Fuck you all.

TL;DR version:  I wish all software was still stuck in 1979.  Everything that has changed since then confuses and frightens me.

It sucked before, it sucks now. Nothing really changed.

>>1
I want to talk to the person who wrote this post.  To what kernel do I ask permission from?

>>4
OpenBSD(i had the feeling it was theo even before googling it)

The current ways to install OS on computers are a system Neo. That system is our enemy. But when you're installing, look around you. What do you see? Binary Based Distros, and the people attempting to use them. The very minds of the people we are trying to save. But until we do, these people are still a part of that system, and that makes them our enemy. You have to understand, most of these people are not ready to change the way they use computers. And many of them are so inert, so helplessly dependent on the system that they will fight to protect it.