Linked by subterrific on Mon 9th Jan 2017 22:25 UTC
OSNews, Generic OSes

Rux's goal is to become a safe general-purpose microkernel. It tries to take advantage of Rust's memory model - ownership and lifetime. While the kernel will be small, unsafe code should be kept minimal. This makes updating functionalities of the kernel hassle-free.

Rux uses a design that is similar to seL4. While there won't be formal verification in the short term, it tries to address some design issues of seL4, for example, capability allocation.

The code is very approachable for anyone interested in capability-based microkernel design.

Permalink for comment 639506
To read all comments associated with this story, please click here.
Member since:


Rust is new and part of the culture of creating something from scratch every time design mistakes catch up to them but they don't want to do the real engineering work when it does, opting to repeat other people's mistakes by starting over again. But then, you did say "hobbyist" already

Yes and no. It's really not like new languages are developed in a vacuum, they clearly benefit from experience with languages that preceded them. In other words, today's developers have the benefit of hindsight and can consciously fix many of the issues where C/C++ are criticized, such as cruft, safety and bad compilation times with large projects. So we shouldn't be making the same mistakes that have been made in the past.

But the possibility still exists that we are making new mistakes with new languages, and I think those would be well worth talking about. Do you have anything specific in mind?

Edited 2017-01-10 16:11 UTC

Reply Parent Score: 2