Commute talk: Why 32-bit? Why not Linux? Serenity Desktop on Linux?


Questions? Topic suggestions? I’ll happily talk about anything. Drop a comment below 🙂


4 thoughts on “Commute talk: Why 32-bit? Why not Linux? Serenity Desktop on Linux?

  1. Totally cool, thought out and logical answers. Had no idea Apple leverages the kernel in the way you describe. Neat. And yeah in the linux model that's a lot of folks all agreeing to an approach.

    It might still be useful and interesting to introduce a wrapper that lets you port BSD drivers across? A lot of that work (writing drivers) is gonna be frustrating and a grind so leveraging existing code and adopting it into Serenity might be a pragmatic approach.

    Really looking forward to seeing where Serenity goes in the next few months, and years!

  2. It's been a while since i've been dabbling with the C++ language, but i believe memory management might be one of the hardest things to handle correctly, at least compared to other languages with a GC or some kind of automatic memory management. Do you find memory management a difficult problem to solve ( maybe not compared to building an actual OS lol )? Do you often experience memory related bugs? Maybe you could talk about or demonstrate how you solve memory in Serenity? Have you looked into other ( newer ) system languages which have better safety around memory management, like Rust?

  3. Here’s another question: Will you port a webbrowser or build an own one? And if you’re going to build an own one, what will you make differently than let’s say Firefox and Chromium?

  4. we get a nice underlying unix foundation.
    a nice UI build by people that actually use the computer and know how the system works.
    everyone can do things everywhere. Wether its making an application or making a new driver
    And this is why serenity is "pretty epic" like pewdiepie says.

Comments are closed.