Rust isn't popular just because of memory safety though. I think the memory safety message is maybe a little too loud.

It's also a modern language with fantastic tooling, very high quality library ecosystem and a strong type system that reduces the chance of all kinds of bugs.

It's obviously not perfect: compile time is ... ok, there aren't any mature GUI toolkits (though that's true of many languages), async Rust has way too many footguns. But it's still waaaaay better than C or C++. In a different league.

▲

uecker 3 days ago | parent | next [-]

Rust is a nice language, but it pushed too aggressively with the argument of "memory safety" at all cost ignoring other considerations. And Cargo is certainly a disaster even though it may be considered "fantastic tooling" by some. In any case, I do not think it is funny that I now depend on packages without timely security update in my distribution. This makes me less secure.

▲

scns 2 days ago | parent [-]

Is there better tooling in C/C++? No snark intended?

	▲	uecker 2 days ago \| parent [-]
		I guess this depends on what you consider good tooling. I am relatively happy with C tooling. But if you want to quickly assemble something from existing libraries, then language-level package managers like npm, cargo, pip are certainly super convenient. But then, I think this convenience comes at a high cost. We now have worms again, I thought those times were long over... IMHO package management belongs into a distribution with quality control and dependencies should be minimized and carefully selected.

▲

hoppp 2 days ago | parent | prev [-]

It can have supply chain attacks like npm... That high quality library system is also a liability.