Thinking about it, it’s weird that there hasn’t been any real change in operating systems for about 50 years. Unix and its derivatives seem to be almost the only game in town, apart from desktops running Windows.
I think the last one to make any real headway was BeOS and they’ve been dying a thousand deaths ever since Apple bought NeXT instead of them. Though admittedly that perspective is coming from a person who used BeOS once in the 90s and has never touched Haiku.
It’s because you don’t want to reinvent the wheel all the time. It sucks doing it. Lots of effort. It’s much better to build on existing stuff and maybe improve it for your needs.
But that’s the thing: is there only one wheel? Maybe wheels are a bad metaphor here, but isn’t it weird, that there aren’t any fundamentally new concepts? Unix was developed basically during the preschool years of computing and we all just kind of stuck with its concepts.
Depends on the level of abstraction you’re looking at. Operating systems today are vastly more capable of organizing different provesses, distributing work amongst multiple CPU cores, CPU caches, etc. I guess the von Neumann architecture has just proven really successful in practice. And von Neumann machines require a certain set of capabilities in their OSes.
Maybe look at embedded systems, where we find a bit more variety. Things like DSPs or microcontrollers.
There’s other engine designs (ex:rotary engine) but the 4 stroke has over a century of testing, improvements, and refinements. A new design can adapt some of the refinements, but would have to catch up on decades of innovation and testing just to catch up!
On the Unix side, there’s the evolution of the Posix standard (which was based on Unix).
I would point out, by comparison, that piston engines are effectively obsolete for certain applications. Most aircraft operate on some type of jet engine, which involves the same core concepts of thermodynamics and aeronautics, but are still fundamentally different. They also optimize for different criteria, which is why neither jet engines nor piston engines hold a monopoly on any class of vehicle.
This is really stretching the computer metaphor. I think my point is that there will be room for rethinking paradigms as our applications of computers grow to include things that weren’t originally planned for. But in a mature technology there’s a lot of established precedent, and that’s not easily overcome. It takes something that can improve the field like jet engines made new aircraft possible.
There was at one time a group pushing to make a more active up to date. User friendly plan 9. Distro if I remember correctly called Harvey OS. They may still be at it. But such a small group means that it’s going to take a long time combined with a lot of effort. And at this point so many things have moved on and become rather linux specific even. That the task only keeps getting more and more difficult.
Honestly, in the interim, many of plan 9’s better features were adopted in some small part or completely by other operating systems. Definitely not quite as elegantly.
What I really want to know is why is nobody here talking about inferno. It’s what came after plan 9.
Sounds like my experience with QNX 6. It was fun for a while, especially with the microkernel novelty. I could kill the mouse driver and bring it back to life. It was interesting to have that on a 486 with memory corruption issues.
It’s legacy, white spaces weren’t allowed as characters on most FTP software, which is how the warez scene shares it’s releases. It used to be underscores, but dots are closer to a white space regarding separation (space wise), so most release groups use dots nowadays.
Generally, a white space as a character in filenames and directories is “frowned upon” in many operating systems, Windows included (somewhat). It makes writing scripts and software more comlicated because it’s used as as a separator for giving command line/terminal options to commands and binaries (programs).
it goes way back before ftp.. i believe its because the original operating systems filesystems/namespacing could not handle the space character at all. so all files lacked spaces in their names. but only for like the first 30 years
Yes, you’re correct, it goes much further back than FTP, all the way down to UNIX I believe. The problem was commands and parameters (options) which use a white space to seperate between them. So, filenames and directories were’t allowed to have white spaces in them.
files.catbox.moe
Oldest