Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • How does this compare to SerenityOS? At a glance, it looks more modern and free from POSIX legacy?
  • Written in Rust. Hmm.

    SerenityOS is written in C++.

    I'd love some kind of meta-language that is easy to read and write, easy to maintain - but fast. C, C++, Rust etc... are not that easy to read, write and maintain.

  • I’m very happy I’m seeing more open source kernels being released.

    More options (and thus) competition is very healthy.

  • > GPLv3 or later (with proprietary driver clarification)

    What's that parenthetical mean?

  • It's comforting to see that capabilities with mandatory access control have become the new normal.
  • So, what's modern about it? "novel systems like Plan 9" is quite funny because Plan 9 is 30 years old.
  • I love seeing projects in this space! Non-big-corp OSSes have been limited to Linux etc; would love to explore the space more and have non-Linux, non-MS/Apple options. For example, Linux has these at the core which I don't find to be a good match for my uses:

      - Multi-user and server-oriented permissions system.
      - Incompatible ABIs
      - File-based everything; leads to scattered state that gets messy over time.
      - Package managers and compiling-from-source instead of distributing runnable applications directly.
      - Dependence on CLI, and steep learning curve.
    
    If you're OK with those, cool! I think we should have more options.
  • This is probably a better introduction it seems, than specifically the kernel of the OS: https://github.com/charlotte-os/.github/blob/main/profile/RE...

    > URIs as namespace paths allowing access to system resources both locally and on the network without mounting or unmounting anything

    This is such an attractive idea, and I'm gonna give it a try just because I want something with this idea to succeed. Seems the project has many other great ideas too, like the modular kernel where implementations can be switched out. Gonna be interesting to see where it goes! Good luck author/team :)

    Edit: This part scares me a bit though: "Graphics Stack: compositing in-kernel", but I'm not sure if it scares me because I don't understand those parts deeply enough. Isn't this potentially a huge hole security wise? Maybe the capability-based security model prevents it from being a big issue, again I'm not sure because I don't think I understand it deeply or as a whole enough.

Explore Birbla archives