3 ms·

The author wrote this on reddit: > What does "Rust-first" mean here? It means not only that both the (micro) kernel and the drivers are implemented in Rust, bu

The author wrote this on reddit: > What does "Rust-first" mean here? It means not only that both the (micro) kernel and the drivers are implemented in Rust, but also that Rust is the first (and only, at the moment) language that userspace programs can be written in. > Although technically one can reverse-engineer the Rust-based ABI and the provided Rust toolchain to write apps for Motor OS in e.g. C, that is some work. But standard Rust programs (using standard Rust library, without FFI) will just compile and run - see e.g. https://github.com/moturus/motor-os/tree/main/src/bin/httpd https://github.com/moturus/motor-os/tree/main/src/bin/httpd. > This Rust-first approach is rather unique, as e.g. Redox uses relibc and C-based kernel ABI as the glue... https://old.reddit.com/r/rust/comments/190znk5/mot%C5%ABrus_os_motor_os_a_rustfirst_operating_system/ https://old.reddit.com/r/rust/comments/190znk5/mot%C5%ABrus_...

glonq 3y ago
> Rust is the first (and only, at the moment) language that userspace programs can be written in. Shouldn't be much effort to make it compatible with Crablang, no? /s
mananaysiempre 3y ago
Unstable, undocumented, compiler-(version-)dependent ABIs are the reason Haiku for x86-32 still has to use GCC 2.95. I’m never not going to welcome a hobby OS, especially in an interesting language (still have fond memories of House). By all means, go for it. Just... it’s important to be aware of the prior art here.
- zokier 3y ago
  Haiku was stuck on old GCC only because they wanted to support old BeOS binaries? But binary backwards/forwards compatibility is not requirement for many use-cases.
  - pjmlp 3y ago
    Haiku without the BeOS applications wouldn't have that much to show. This is the way to go on platforms that favour shipping binaries instead of source code. Outside Linux/BSD, stable ABI across OS versions is a concern, hence why Apple, Google and Microsoft platforms all offer ways to keep this going.
ahepp 3y ago
I thought the Rust ABI wasn't even stable?

glonq 3y ago

> Rust is the first (and only, at the moment) language that userspace programs can be written in. Shouldn't be much effort to make it compatible with Crablang, no? /s

mananaysiempre 3y ago

Unstable, undocumented, compiler-(version-)dependent ABIs are the reason Haiku for x86-32 still has to use GCC 2.95. I’m never not going to welcome a hobby OS, especially in an interesting language (still have fond memories of House). By all means, go for it. Just... it’s important to be aware of the prior art here.

zokier 3y ago
Haiku was stuck on old GCC only because they wanted to support old BeOS binaries? But binary backwards/forwards compatibility is not requirement for many use-cases.
- pjmlp 3y ago
  Haiku without the BeOS applications wouldn't have that much to show. This is the way to go on platforms that favour shipping binaries instead of source code. Outside Linux/BSD, stable ABI across OS versions is a concern, hence why Apple, Google and Microsoft platforms all offer ways to keep this going.

ahepp 3y ago

I thought the Rust ABI wasn't even stable?