This is a peculiar comment. Why would you think readers are seeking a balanced 'view of the industry' here? HN is much less bland than that. The guidelines have

This is a peculiar comment. Why would you think readers are seeking a balanced 'view of the industry' here? HN is much less bland than that. The guidelines have a view on what's relevant content here: If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity (https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html). 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?