> Just as no sane person would pick up Rust to write generic web services in that scenario. I agree, but that's the thing... people DO advocate for that! http

> Just as no sane person would pick up Rust to write generic web services in that scenario. I agree, but that's the thing... people DO advocate for that! http://www.arewewebyet.org http://www.arewewebyet.org Of course, there's a lot of double-talk on the subject. "You can TOTALLY do it today!" ... "Eh, but maybe you wouldn't want to use it PRODUCTION today" ... "But we're just a FEW more crates away from being there!"", etc. The Rust community is great, but they seem they hedge their bets too much and are murky with the messaging. Right or wrong, Rust and Go compete because there are a LOT of web and microservice developers out there (including me) who: 1. Love what Go brings to the table in terms of of type safety, and AOT compilation to single-file native executables... 2. ... but wish that Go had more functional-style constructs (filter, map, immutability, etc), generics, a contemporary package system that doesn't involve putting Git URL's in your actual source code... or any of Rob Pike's other stubborn alien quirks that people don't like. Rust can't quite figure out whether it wants to market to this crowd or not. Sadly, due its learning curve, I DON'T believe that Rust is the answer for the "Go, but with more popular features" problem. But enough people aren't ready to concede that yet.