[anoncow]

As someone with very little expertise in this, and from the very little time that I can spare for experimental webdev, from a webdev framework perspective, Rust is where Go was 7-8 years back. There are some Rust frameworks available which look promising (rocket), but golang has much more. On the flipside, There is nothing wrong with golang (or at least it has less wrong going for it as compared to the js frameworks), but Rust is appealing because it IS the next big thing.

[zelphirkalt]

I think you need to qualify the aspects, in which you think Rust is 7-8 years back. I rather have the impression, that the designers of the Go language had a too simplistic view of what Go should offer and then it took them 12 years to get something as common as generics. Rust has many language features and of course had generics waaay before Go. In general it seems the Rust ecosystem does sometimes have things later, but therefore better or correct when it arrives at a solution. In terms of language design Go is the one that seems way behind.

[pram]

Shocking but true: you could program things in Go before generics.

[erik_seaberg]

Now a pile of legacy code needs to be burned to the ground and replaced (it sounds like a lot of Kubernetes was generated to work around it). In the Java ecosystem we’re fortunate that this is long since finished.