Rust in 2025: Targeting foundational software

28 wseqyrku 4 8/16/2025, 5:45:00 PM smallcultfollowing.com ↗

Comments (4)

themafia · 24m ago
Rust in 2025: Still putting the cart before the horse.

How about get an actual published language standard? How about get more implementations of it? How about fix the utter mess that is cargo?

Nope.

"Let's replace everything else. Let's be 'foundational.'"

Rust is a language for people who want to be _seen as programmers_. Not people who _actually love programming_.

aw1621107 · 4m ago
> How about get an actual published language standard? How about get more implementations of it? How about fix the utter mess that is cargo?

I think these arguably also warrant a "is this putting the cart before the horse?" analysis. I think the value of all of those are pretty debatable (especially in different fields), and I don't think it's at all obvious that Rust would have done any better had it devoted more energy to those earlier in its life.

Also, I think that the article is technically compatible with working on those points anyways?

> Let's replace everything else.

I don't think that's what the article is trying to say? "Targeting" here seems to be more in the vein of "usable for", like "target" in "this language targets this use case".

camjw · 4m ago
What are your specific gripes with cargo?
vlovich123 · 12m ago
> Rust is a language for people who want to be _seen as programmers_. Not people who _actually love programming_.

Nice gatekeeping. I happen to actually love programming and I pick up languages quickly. Rust has been a fresh breathe of air and I can’t ever see myself going back to the horror show that is the masochism of C++.

> How about get an actual published language standard?

https://rustfoundation.org/media/ferrous-systems-donates-fer...

But also a language standard means fuck all to me. C and C++ keep generating them and the language doesn’t seem to be getting meaningfully better.

> How about get more implementations of it?

Why is this important? Python has one central implementation that everyone relies on. So does Java. C++ doesn’t and is plagued by every project either trying to support N platforms across M compilers or just pick clang everywhere (but still be stuck with having unnecessarily complicated platform specific code).

> How about fix the utter mess that is cargo?

What’s the utter mess? I’ve been using it for a while and haven’t observed anything obscenely problematic. Significantly easier than anything in C++ for sure (maybe Conan but I’ve not seen anyone actually using that in the wild)