Nobody seems to realize how truly ancient Linux is. We're living in the internet age when 5 years is a long time and 10 an eternity, yet Linux is over 40 years old. It wasn't known by that name 40 years ago but that hardly matters since it's hardly changed since. Linux dates back to a prehistoric era when computer dinosaurs roamed the Earth and stern patriarchs ruled the home. And it shows!
Linux has 40 years' worth of mistakes and missed opportunities accumulated in a gigantic pile of crap. First was refusing to use a capability security model in favour of intrinsically broken access control lists. Oh sure, the morons at the time didn't know ACLs were intrinsically broken. What they DID know was that ACLs appealed to evil totalitarian power-hungry pieces of shit. Far from taking the hint, they considered it a plus! Which is why Linux's model of users is still based on Fascism.
Stalin would approve of a unique special super-user that has total control over every other user's existence. Everything from creating users to parceling out resources to controlling which groups exist and who belongs to them. Approve? That's putting it mildly. Stalin could only DREAM of having this much power. Yet moronic programmers don't think twice about the dictatorship that's hard-coded in this supposedly "multi-user" OS.
Apparently, not only do most people think totalitarian dictatorship's a fine solution to political problems, they also think it's the first and best solution. Something de rigueur and hardly worth mentioning. My mind boggles.
The second mistake was becoming wedded to an intrinsically decrepit low-level programming language. I'll remind you that LISP had already been invented by then so it was clear that C was horrifically low-level. That too was considered a plus! But it didn't stop there since Ken Thompson made his inability to grasp higher-level abstractions blatant when he went on to create Plan 9 at Bell Labs.
Plan 9 is "what Unix should have been". It is an abject failure even by Thompson's rather miserable standards (processes aren't really files in Plan 9 and can't be copied using file tools). In 1980, Xerox PARC released Smalltalk-80. Did Ken Thompson learn anything from it? Fuck no. Throughout the 80s and even in the late 90s when object-orientation was the buzzword of the day, the whole concept of objects was completely beyond Ken Thompson. You see, he was still obsessed with FILES.
The fact that Linux failed to stick to its paradigm of everything-is-a-file when the need for a graphical system came along never made Thompson think twice about whether this pathetic files+bytestream filters paradigm was good enough. The fact that Smalltalk was awe-inspiringly beautiful apparently never crossed his mind either. No, he spent over a decade trying to redeem his failure. Trying to prove that he wasn't some overpaid loser that got lucky and struck it rich.
Which just goes to show: living in the past doesn't pay off, it only proves you're a loser has-been incapable of moving on. Ever heard of "moving on" Ken? Bah, never mind. Alan Kay never learned to move on after his failure to create a programming language for children either. Hint: it can't be done because half the population lacks analysis and can't master programming at any age.
That's another thing, Linux grew up long before 2D graphics was a gleam in anyone's eyes. And it never, ever integrated it. X Window is a piece of crap that's officially "not part of the operating system" despite the fact it had to run as super-user with the ability to crash the machine at will. This was considered a plus!
That's right, just because a major piece of the programmatic base of the machine violates ALL OF the fundamental principles of the OS, that's no cause for concern. Just say it's "not part of the OS" and you can pat yourself on the back for fixing the problem. And who cares if they don't integrate together?
I mean, it's not like anyone would ever want the window they're using to be given absolute priority by the machine! It's not like Linux is suddenly an interactive operating system just because it's suddenly got graphics. Who cares if windows suddenly become unresponsive? Batch processing and teletypes are so much better! It's not like users want to actually be in control. It's not like they want the machine to be responsive.
More than 25 years later, and Linux still can't handle 2D graphics correctly. How many years has it been since 3D graphics became commonplace? At the rate it's stagnating, Linux will have integrated 3D graphics in about 100 years. That's 50 years for the first half-wit systems developer to grasp what 3D is good for in operating systems, and another 50 years for Linux to get it. So yeah, in the year 2110, Linux might be fit for use by our generation.
Metaphors Make Bad Models
Let's not even go into the "desktop" and "office" metaphors. Because the whole notion of using, let alone relying on, metaphors in systems design is vile, repulsive and disgusting. It's the kind of crap that ought to get your design credentials revoked for life. Yet again, software developers consider it a plus! Then again, software developers have always been pretty contemptuous of everyday users.
Fucking "icons" as if users were weak-minded retarded morons who can't possibly learn what an object's representation means without it superficially resembling something completely different they're already overly familiar with. You'd almost think users were as retarded as software developers. That'll be the day. When users spend all of their time on projects 90% of which fail to deliver any value to anyone then we can start comparing users to developers.
Fucking technological obsession, as if there weren't perfectly good buttons on the keyboard to use in concert with a button-less mouse. Ever heard of synergy?! It's a word. If you don't know what it means then go back, back to the 80s! But no, a mouse is a Holy Technological Artifact and a keyboard is a Completely Separate Holy Technological Artifact, and never the twain shall meet in the mind of the users. Why, it would be sacrilege!
Ever wonder why there has to be a metaphor of the physical mouse inside of the user's model of their workspace? I did and the answer is obvious: because software developers are too fucking stupid to understand "the user's model of their workspace". In fact, software developers are too fucking stupid to understand that what's inside the computer isn't their workspace!
Proof: you only have one mouse, so you "should" have only one mouse pointer, right? Wrong! You should have two. That way you can swap between them at will. You leave one somewhere then swap and move the other one to the other end, then hit some key (on the keyboard) and all the objects between your pointers get selected. It is fucking obvious when you think about it. It is fucking obvious when you're unhappy with drag-selection being modal and bother to spend just a few hours coming up with something better!
Yet it's equally "obvious" to an OS developer that what's inside your workspace really belongs to them. They're programming software drivers for one mouse so in their atrophied minds, it's obvious there can only be one pointer. Never mind what's in your mind, because you don't matter!
It's amazingly difficult to convey exactly how ancient, how capricious, how fucked up, and how totally dysfunctional this piece of crapware called Linux is.
It's vile, incoherent, inconsistent, contradictory, meaningless, arbitrary, senseless, ad hoc, unprincipled, bloated, arrogant, dictatorial, fetid, rotten, corrupt, and just plain evil. That's when it's working. When its laughable insecurity (called "security" for some incomprehensible reason - I suppose it sounds better) hasn't been cracked open like an eggshell, your computer crashed and all your data corrupted.
And do you want to know why? It's because software developers are egotistical pricks. They have the same cognitive type as engineers, physicists and economists. But they have fewer limitations imposed on their work. They don't answer to physical reality, they don't answer to their peers thirsting for power & knowledge, and they don't answer to rich & powerful masters wanting to oppress the poor. They answer only to themselves. And that's why Linux is a pile of decrepit unusable crap.
To a software developer, running amock having "fun" is called hacking ... and it's a plus!
A warning to the people
The good and the evil
This is war