Eh, depends on where you work, in gamedev land we loved to play fast & loose with nightly/etc(within reason). Heck, I'd argue that crowd is even wilder than the

Eh, depends on where you work, in gamedev land we loved to play fast & loose with nightly/etc(within reason). Heck, I'd argue that crowd is even wilder than the JS ecosystem, it's just not as public. Really, you might want to check your echo chamber a bit. Native programming is not the norm in the industry, most fresh grads have touched C or C++ once or twice and know the theory but none of the practice. Heck back when I was in college we had people coming to our community college to take the C course there since UCSD didn't offer it as part of their curriculum. Now, does the majority of software run on C/C++ based systems? Totally. However I would posit that the number of people who build those systems is much smaller than the number of people working in Java/Javascript/Python/C#/PHP/Ruby/etc. Your LoB app doesn't need the performance of C++, you just use a DB that's built with C++. You may use ngnix but the webserver behind it is probably written in Java. There's an inverted pyramid in software. The lower down the stack you go the more specialized and domain specific you get. Component/app/framework reuse means that you need less people at the bottom then you do at the top otherwise we'll all be fullstack web/frontend/backend/driver/kernel/vhdl developers. Either way I think Rust has a rich and vibrant community which isn't going away anytime soon. Would it be nicer to see wider adoption? Sure, but I'm not worried about it either.