[0] https://survey.stackoverflow.co/2024/technology#most-popular...
But the moment you search Rust on LinkedIn, you can see the truth.
> Which programming, scripting, and markup languages have you done extensive development work in over the past year, and which do you want to work in over the next year?
It does not ask if you are gainfully employed and using this language for your job.Also, in the same results, just above Rust, I see:
> PowerShell 13.8%
<sarcasm>
So, I guess that we can safely say that Microsoft PowerShell is still more popular than Rust.
</sarcasm>The annual survey is very popular in the Rust community. Its results are often used for advocacy. Participation by Rust developers is very high. So what you have is a classic case of a selection bias.
It just takes time to defeat the 40+ years of c and c++ dominance.
(Yes, I'm familiar with the rich ecosystem around helping devs not write crummy C. I worked at Coverity at one point. If anything, that gave me enormous fear and respect of the hoops you have to jump through to be reasonably sure C code isn't completely broken.)
Glancing at random C code tells you nothing about what happens with the data flowing into and out of it.
In my experience with it, rustc has been insistent on making me write code that's actually correct. I could translate that code back to C and have better C code than I would likely have written on my own. If there were something similar to `gcc -Werror -Weverything-rust-would-complain-about` — and if that thing were even possible — I very well might stick with C. Oh, and something as fast and ergonomic and informative as rust-analyzer would be hugely welcome.
You have a single line serialization into/from absolutely anything. You have logging, tracing, cli libraries, error handling - most of those are one liners.
You have enums. Enums are business logic. Enums are often the way the world works.
You press enter and it builds, no pre setups, sub modules, cmake files and whatnot.
I like F#, Haskell, Elixir but not Rust.