We could easily have done so in Java, but we'd be in Java's concurrency model, which is much more difficult to reason about.
I think this is exactly what people mean when they say Go is more of a replacement for Java than it is a replacement for C++: In the sense that when Ruby and Python become too slow, people normally reach for Java, but now they have Go as an alternative option, with a better concurrency model than Java's.
Better language? Not really, if you want types TypeScript is a much better option. With node+typescript+react you can get end-to-end typechecked code with no FFI involved - thats really, really cool.
Better concurrency? Oh yeah, definitely. Better core libraries? Yes, by far.
Better package ecosystem and management? Definitely not.
> Better language? Not really,
There is no conceivable universe in which the expression "JavaScript is a better language than Go" evaluates to true. ~$ node
> "JavaScript is a better language than Go" ? true : false
true
> "JavaScript" > "Go"
trueWe can argue that the Go concurrency model is better.I think nodejs's is good enough,easier to understand and to deploy. If your goal is to write lightweight webservers that do a specific task,nothing beats node in my opinion.
Ehm, really? Tree of javascript, possibly with some compiled libraries easier to deploy than a static binary?
I'm not saying node is hard to deploy, but I think maybe I'm misunderstanding what you mean here?
I don't see any web technology Go could replace. Not even dynamically typed langauges.