another rust hype article.
with all that, readers of likes of hn, certainly would have a skewed view of industry.
I'm not really sure what you're expecting. Haskell gets a vastly disproportionate amount of time here compared to it's actual usage also, and PHP gets almost no coverage at all, but we all know it's out there in force, and so are the people that program it. Should we be pushing for a lot more PHP content? What about COBOL content? That's still in use, and I can't remember the last time I saw a submission about that.
www.paulgraham.com/pypar.html In Python Paradox, the author argues that it's a signal of quality that someone would take the time/effort to learn Python. (Python is new and wouldn't land them a job).
Now in 2019, Python is popular. But I think it's fair to say instead that Rust wouldn't be a good choice if you wanted to get a job using a language which is popular in the industry.
1. I want to add a low(er) level language to the ones I already know and use.
2. Though I did some C/C++ in high school, getting really into depth with C++ at the moment seems really daunting.
3. I don't need it for a job at this point so I can afford to learn a less popular language that can potentially have a future and which exposes you to new ways of thinking about code.
In my case with the devs I hire the only thing I care is that they want to work in a class of languages, like frontend or backend, and that they're not super picky.
I'm hiring people to solve problems for a living. I have full confidence that anyone I hire can learn any language I throw at them. My job (when hiring) is to make sure they'll want to work in the area, maybe a footnote about the language (if even known), but that's all.
Why does language matter so much to some people (as far as hiring goes).
Do you have some particular animus against Rust, or do you think it's some sort of general rule that developers should learn only the 'top 5' 'industry' languages?
I've started learning Rust, for a few reasons:
- I read a couple of chapters of Steve Klabnik and Carol Nichols' excellent "The Rust Programming Language" a while back and enjoyed it so much just as a book that I promised myself I'd read the whole thing when I had time. Now I do, so I am.
- Rust instantiates some concepts that I'm familiar with but only at a vague hand-wavy level. Learning it is educational (for me).
- Rust is used in some open-source projects I'd like to contribute to if I can.
- I have a couple of personal project ideas in disparate areas (wasm, embedded) that Rust seems well suited for
It's quite likely I'll never use Rust in a job. So what?