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 639507
To read all comments associated with this story, please click here.
Member since:

today's developers have the benefit of hindsight and can consciously fix many of the issues where C/C++ are criticized over cruft and lack of safety. So we shouldn't be making the same mistakes that have been made in the past.

It's the way they go about fixing the issues - "oh, we'll just create yet another language" - that is the problem. All languages will develop cruft, and all languages will paint themselves into a corner. The most ideological ones tend to do that the most frequently.

Only a handful of languages are left where the base is committed to using it cruft and all and not just abandon it for the latest fad in language design.

Reply Parent Score: 2