rustix VS RIIR

It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.

Found this as well: https://github.com/sunfishcode/mustang

Some discussion here: https://github.com/bytecodealliance/rustix/issues/76

Without actually having looked into this, how does https://github.com/bytecodealliance/rustix fit into points 1 & 2?

I find this github issue: https://github.com/bytecodealliance/rustix/issues/575

Hi Rust experts, we are willing to integrate rustix on NuttX RTOS, the initial effort was done by rustix author: https://github.com/bytecodealliance/rustix/tree/nuttx but it hit the wall since we don't know the right way to integrate cargo with the old-school NuttX's Makefiles. Any help or suggestion is welcome. More about NuttX here: https://nuttx.apache.org and here: https://nuttx.apache.org/docs/latest/

Have you considered using rustix? It provides many of the facilities of std without using libc.

rustix can make syscalls directly to Linux. There's a rustc fork that can use it to build std.

The rustix project claims to use raw syscalls (and vDSO calls) on linux and provides more memory / type safety compared to the libc API.

Hi, the reason is explained by the description of https://github.com/bytecodealliance/rustix.

Please consider rustix as an alternative to nix.

It was, imo, inflated by the comments pointing to the RiiR sentiments, not the comments to that effect itself. Even repositories 'collecting' such instances (e.g. https://github.com/ansuz/RIIR) are largely not collections of making anyone to change their own software but just projects that happen to be written in Rust. (these out-of-scope issues are not being tagged appropriately). Overhyped controversy by all sides.

Dunno what news you have missed but there's entire internet brigades dedicated sorely to spam projects with "rewrite it in rust". There's even a repo documenting this.

The OP post in the link references https://transitiontech.ca/random/RIIR (Rewrite it in Rust) as a meme.

Yes, one can hope, but I wouldn't bet on it and I wouldn't suggest to RIIR. I don't want to be that person that pops up uncalled for and asks to Rewrite It In Rust. One might think "Oh it is just one additional issue to the ~2.2k already opened mypy issues" if they have at all realized that there are that many open issues.

It's died down a bit now, but there is/was a non-trivial amount of stupidity from Rust advocates whenever someone ran into a memory problem with C/C++ to "re-write it in rust" or to just rewrite things in general. (IE https://transitiontech.ca/random/RIIR)

Or even better, RIIR the Windows kernel!

What is it with people asking for rust rewrites of Xorg this week? https://github.com/ansuz/RIIR/issues/83

The second language is Rust, and I went with that partly because rewriting C in Rust is a meme in itself, and in part because it was much easier to think of how to nicely fix that bug in Rust than it was in C (just add a = to the range to be end-inclusive).