[bsaul]

i don't think you can "catch up" with go, because it has aimed at being minimalist. catching up by removing major features to a language isn't something i've ever witnessed.

[camus2]

> because it has aimed at being minimalist.

You can absolutely catch up with the concurrency model, on the single binary deployment, and a other features. Go isn't "minimalist", that's false, go look at the reflect package, it's complex as hell.

[golangnews]

I’ve used go for around 5 years on multiple large deploys without touching the reflect package. It is neither recommended nor necessary.

Go is radically minimalist compared to other languages - it leaves a lot out, most notably inheritance.