> awk, bc not production level languages. I think you're being disingenuous there. First of all, we are talking about programming languages here, not about how

> awk, bc not production level languages. I think you're being disingenuous there. First of all, we are talking about programming languages here, not about how widely they are used in "production". I know that awk is used in one giant company to do an important thing (aka dealing with money). It wouldn't surprise me to find that bc is also used in "the industry". On that note, the TIOBE index lists Java, C, C++ and C# as being the most widely used languages. Awk is number 33, just below Ada, Prolog and Erlang. Rust is not even on the list, a list where assembly of all things holds the 14'th place. (bc is in the same group as rust there) Erlang is also used for plenty of "heavy" things, notably in the telecommunication and banking industries. Haskell is used by facebook for their spam filter. WhatsUp is written in erlang. https://www.youtube.com/watch?v=LnX3B9oaKzw https://www.youtube.com/watch?v=LnX3B9oaKzw > If you know anything about both languages that's at the top of their features list, which I mentioned. Not everything is about "features". > If concurrency units (threads, co-routines) share a heap they are not memory safe. If you want to talk about concurrency you should mention "Communicating sequential processes", where from Rust did take some wisdom, but Go (as a popular example) went full in. Functional programming (lamda calculus) also lends itself extremely well to "threading", intrinsically so. I think that discussions are about learning things, clarifying things and such "nonsense". But this discussion seems to be all about "winning at any cost". So.. goodbye.