Legacy

how dare you 😧

Linux kernel Rust is special because of using the kernel's memory model instead if Rust's, not because they don't use external crates (they actually do vendor a few).

no_std or no external crates doesn't alone qualify as special.

If it's similar to the kernel policy, they can incorporate desirable crates in-tree if needed. A crate is just a modular unit after all. And what's more relevant here is std/no-std dependency assumptions.

References about external crates usually mean avoiding "crates.io" in the build process, not avoiding crates themselves as modular units.

And even if a crate is not fully incorporated, modules from it can be copied (and possibly modified) still, as people in the real world tend to not re-implement stuff from first principles 😉

rustix supports no_std. spin too. And there are others. Those are the good low-level crates. A hard dependency on std is itself an indication that a crate is not really low-level.

The announcement doesn't say core only btw. alloc is there too which is very relevant. So this doesn't filter out anything from the no_std world.

But this is all about ecosystem choice subtleties, not some change in how the language itself is used, which is why I found your comment amusing.

as a Rust dev, it also sounds like I would struggle…

It's literally Rust. If you actually knew rust, why would you struggle?

You’re using the syntax and presumably compiler (rustc)

but almost nothing else from Rust

waat 😲

That's python's problem. You have no idea how much of a life improvement simply using uv + an older python version (uv natively supports this) is.

All major distributions ship their own compiled rustc/cargo packages already, and they've done so for years.

And putting rust projects using nightly features aside*, stable rust version updates are much less disruptive than major GCC or clang updates. Breakages are rare, known in advance, and communicated to upstreams before hand (look up "crater" if you want to learn more).

* Not sure if distros package, or need to package any such packages, but I didn't do any surveys on the subject.

This has been happening forever. This old post always pops up in my mind for some reason as a historic example from an earlier linux boom.

Unfortunately, people have been pushed to not call out such things, because it's "not nice", when as the blog above shows, not calling it out is what's not nice, and potentially dangerous.

More obvious, but systemd has a lot of features that a simple cron doesn't.

Which cron?

Oh wait. Why did I assume OP would know there are multiple implementations? 😄

muh io bound

🤣

If the DB is IO-bound, and "slow languages" don't matter because "IO bound", then show me the DB you're using implemented in a slow language.

It's hilarious how op is being this stupidly unaware, even within his stupid false argument which is provided as a supposed given.

How are people seriously engaging with this blog fart full of false premises and contradictions?

You seem to be confused about what Signal protects against, or claims to protect against.

None of the items from your list apply. Maybe you're confusing it with another distributed solution with peers connected through anonymous transport.