BeOS DEMO VIDEO

Futurama reference ;) [link] though apparently popular enough that some people have made all-rush playlists ( [link] ) On-topic - definitely a cool project and one that I haven't heard about actually, added to my queue of weekly source-code readings. I'd also consider DirectFB similar, and another project that I just have in my vaguest of memories (think they used a project-name like Cairo that got google-CVed out of existence from the more recent one) from the 2001-02ish era. They tried to attack X back then, but fell victims to the driver situation (but they had arbitrarily rotated windows!). One of my stronger personal influences is BeOS though - Compare ▶ this video to [link] :)

in “I wrote a display server, a desktop environment, and a debugging/reversing tool” · View on HN

If we're talking tech, then your post couldn't be more wrong given my BeOS and QNX examples. Performance was equal to or better than monoliths of the time. BeOS especially destroyed competition in concurrency performance due to its architecture. QNX runs at hardware speed basically with real-time properties and POSIX support. BeOS disappeared due to Microsoft monopoly with Haiku making a OSS clone. QNX was at $40 million a year in revenue when Blackberry bought it. Green Hills and VxWorks are doing OK, too, with VxWorks making more than QNX per quarter. Both have desktops virtualizing Windows, Linux, etc on microkernels w/ Gbps throughput. I don't see why we keep getting these theoretical counters given the proven results of microkernel performance in the field. Tell me why microkernels are too slow when they can only do this on 90's era hardware: ▶ this video Then, tell us why we should sacrifice isolation of malice and faults in favor of kernel-mode code with properties like this: [link] Our side produced highly reliable and secure systems plus high-performance systems. It was always done with a small group with little time. The monoliths took a decade and thousands of man hours to do the same. It's up to you people to justify why those hours were well-spent. "while for say an exokernel the opposite is mostly true." An exokernel is a microkernel...

in “Redox – A Unix-Like Operating System Written in Rust” · View on HN

Not organized to be able to just throw out a reference and many disappeared over time as old web faded. It's more something you see relative to other OS's than an absolute. I really need to try to integrate all the examples sometime. Here's a few, esp from past, that give you an idea. Historical look at quite a few [link] Note: A number were concurrency safe, had a nucleus that preserved consistency, or were organized in layers that could be tested independently. UNIX's was actually a watered down MULTIC's & he's harsh on it there. I suggest you google it too. Burrough's B5000 Architecture (1961-) [link] Note: Written in ALGOL variant, protected stack, bounds checks, type-checked procedure calls dynamically, isolation of processes, froze rogue ones w/ restart allowed if feasible, and sharing components. Forward thinking. IBM System/38 (became AS/400) [link] Note: Capability architecture at HW level. Used intermediate code for future-proofing. OS mostly in high-level language. Integrated database functionality for OS & apps. Many companies I worked for had them and nobody can remember them getting repaired. :) Oberon System [link] [link] Note: Brilliance started in Lilith where two people in two years built HW, OS, and tooling with performance, safety, and consistency. Designed ideal assembly, safe system language (Modula-2), compiler, OS, and tied it all together. Kept it up as it evolved into Oberon, Active Oberon, etc. Now have a RISC processor ideal for it. Hansen did simi

in “Unikernels are unfit for production” · View on HN

I didn't know about BeOS booting process, but I stumbled upon good old demos[1] recently, I remember how I was amazed back in the days. I'm still amazed, more than before. Sad. [1] ▶ this video

in “Experiment in booting Linux fast” · View on HN