A Re-Implementation Of The EROFS File-System In Rust Has Started

[phoronix]

Phoronix: A Re-Implementation Of The EROFS File-System In Rust Has Started

The EROFS read-only open-source file-system has seen initial patches posted today for beginning to re-implement the C code within the Rust programming language for better safety guarantees and the possibility of more performance optimizations...

https://www.phoronix.com/news/EROFS-Rust-Code-Starts

[milkylainen]

I'd rather waste my life writing something new instead of rewriting existing things.
Maybe that's just me.

[varikonniemi]

Would be nice if phoronix would tell how many LOC of C this 3k of rust code is replacing.

[oleid]

Oh yeah, another thread for a flamewar. Great.

[davidbepo]

rust fanboys make something new instead of wasting effort on rewriting the universe in rust challenge (impossible)

[bacteriamanicure]

rust fanboys make something new instead of wasting effort on rewriting the universe in rust challenge (impossible)

How else are we gonna prove to C fanboys that Rust is production-ready? Can't prove that Rust is suitable for filesystem drivers without a filesystem to drive.

[kpedersen]

rust fanboys make something new instead of wasting effort on rewriting the universe in rust challenge (impossible)

They can't. They need to wait on the abstractions^W bindings first. And since this is kernel land, they can't just do what they usually do and drag in a load of shite from crates.io to provide them.

This also isn't intended to be a re-implementation at all. It is merely replacing a few selected functions via Rust since the VFS bindings aren't in place yet to do a proper job.

[KernelCrasher]

What a summit of old farts complaining about other people's choices how to spend time. Go do something, stop whining.

[Britoid]

I think rather than replacing existing drivers, alternative ones or a new kernel should be written in Rust instead.

I fear this will alienate existing maintainers who do not want to learn Rust and have had decades of experience writing kernels/drivers. Plus for when the next language comes along that people over-hype (e.g. Zig), everyone can move on without much hassle.

[bacteriamanicure]

I think rather than replacing existing drivers, alternative ones or a new kernel should be written in Rust instead.

I fear this will alienate existing maintainers who do not want to learn Rust and have had decades of experience writing kernels/drivers. Plus for when the next language comes along that people over-hype (e.g. Zig), everyone can move on without much hassle.

1. Linus, the first maintainer, wanted Rust
2. Redox apparently exists
3. You're using Rust right now so idk if it's much of an overhype

Also imagine thinking C fanboys aren't alienated just by having other letters