Several of the roadblocks you mention can be worked-around using things like Rc, RefCell, and Cow. By default these will still make things more verbose than lan

Several of the roadblocks you mention can be worked-around using things like Rc, RefCell, and Cow. By default these will still make things more verbose than languages that are GCed, but they free up your overall architecture to do things the way you'd expect to do them in those other languages. And these are just the standard-lib baseline: with macros, traits, and careful use of unsafe {} inside your own abstractions, you can make more things implicit and ergonomic than the base language allows by default. Rust is definitely not yet as ergonomic as something like Node for writing web servers. Even if Rocket were 100% production-ready, I probably wouldn't recommend it over a GCd language in my own organization unless we needed a) crazy performance or b) crazy type-safety. But could Rust get there one day? > I suppose I stretched calling it "unrealistic" for Rust, since, well, look where it is; I guess it's more just a position I don't understand or agree with I would call Rust's attempted breadth ambitious. I think it's charting new territory and I'm very curious to see how far it will be able to stretch. I don't know the outcome here; nobody does. It's very possible it will never take off for mainstream web dev and will be confined to systems, tooling, etc. But I think there's potential, and I think it's too early to call.