Earlier quoted context omitted.
I've been dreaming of a fully rebuilt hacker-friendly OS for a while. Trouble is, it's hard to justify development, even for FOSS, unless you can find some kind of hook for the mainstream, for reasons that may not seem apparent at first. Chief among these concerns: isn't it a little insular to create an OS that will only be used by people with the utility to write their own software? At some point, the software must…
Really at this point it's fair to say the the current Linux desktop stack is already a miracle; a backwards-incompatible rebuild is just impossible, or at least with the current state of the mainstream UI development tools. Which, on the other hand, I think is rapidly evolving, now that OOP is out of its hype phase, and can now be evaluated a bit more (pun almost intended) objectively, and freed from its unnecessary…
I think the main scripting language for an OS should at be considered near-perfect when the OS begins - like C for Unix. One of the design goals for that language should be to work well for graphical UI - imagine if a framework like React had a language designed around it instead of being shoehorned onto JS. We could start talking about ideas like separating the layout, styling, and interactive components in a better balance than that between HTML, CSS, and JS.
Really my main point is - There's a conversation to be had around starting from (near) scratch. I think in the end a lot of *nix would have to be incorporated to deal with the realities of hardware and established protocols, but we could also look at starting in a VM and working towards bare metal. Or cave and include POSIX-style standards in a way that is not limiting to desktop OS design.