If you need a yacht that can carry many people on the high seas through bad weather at speed, unix is solid. But there hasn't been a great racing dinghy since the 80s.
Maybe there is an demoscene/hacking tradition out there, waiting for to be discovered.
Consider the debates that we don't have:
* Hardware abstraction. Casual audio programming is harder now than it was twenty years ago. Also - why doesn't hardware self-describe?
* High-level languages. Chuck Moore's ideas of code bloat are on a totally different level to the mainstream. He's onto something.
* Protected memory. Does it matter on a machine designed for fun? How much more hackable could your OS be if you got rid of stuff like this?
Stability doesn't matter so much in fun systems. If you're in a dinghy and not capsizing, you're not sailing hard enough.
Thanks for the link, very interesting. Have you read Massalin's thesis on Synthesis OS (Partially Evaluated/JIT kernel objects) ? It's from the late 80s and very 'demo-scene' like (The author mentions efficient audio playing through his object based system).
If you need a yacht that can carry many people on the high seas through bad weather at speed, unix is solid. But there hasn't been a great racing dinghy since the 80s.
Maybe there is an demoscene/hacking tradition out there, waiting for to be discovered.
Consider the debates that we don't have:
* Hardware abstraction. Casual audio programming is harder now than it was twenty years ago. Also - why doesn't hardware self-describe?
* High-level languages. Chuck Moore's ideas of code bloat are on a totally different level to the mainstream. He's onto something.
* Protected memory. Does it matter on a machine designed for fun? How much more hackable could your OS be if you got rid of stuff like this?
Stability doesn't matter so much in fun systems. If you're in a dinghy and not capsizing, you're not sailing hard enough.