←back to thread

207 points krustowski | 1 comments | | HN request time: 0.214s | source

To try it out, simply build the project yourself from source, or use attached bootable ISO image of the system (in Releases on Github) and run it in QEMU.

https://blog.vxn.dev/rou2exos-rusted-edition

Show context
rollcat ◴[] No.44319184[source]
Memory-safe language. x86_64, with Arm on the roadmap. Networking stack. Boots from a CD and via multiboot. Your hobby project wipes the floor with DOS.
replies(2): >>44319373 #>>44325055 #
MoonGhost ◴[] No.44325055[source]
> Rust and x86 assembly

then

> Memory-safe language.

What's the point? Looks like today Rust is like 3D printing was. As if it makes something better. Printing was hyped and advertised by printers sellers and manufacturers. Finally they run out of money.

As for project, it's cool if compatible with old soft. Otherwise suitable mostly for education and masochism. Long way to become practical anyway even if it gets traction.

replies(3): >>44325086 #>>44325165 #>>44326137 #
1. whytevuhuni ◴[] No.44325165[source]
The idea of Rust is not that it is 100% safe, but rather that it is able to encapsulate unsafety and divide the program in two parts:

- unsafe code plus modules that support it (the "trusted base")

- all the rest

Rust's promise is that there is no way to trigger any undefined behavior from bugs happening in "all the rest" of the code. If that code makes for more than 95% of the total, then that's a huge win compared to a completely unsafe language.

Also, Rust's support for inline assembly is in my opinion better than C's, it's much easier to specify and figure out the constraints on the boundary between Rust/assembly.