Comment on: Does the Go programming language have any future?
The first two problems are to be expected of any new language (e.g., Rust, Swift). The third point seems backwards to me: isn't it good that it breaks with traditional paradigms? What's the point of making a language that's just a nicer C? Can you say what specific aspects of Go you didn't like, and why?
The type system is lightweight, and deliberately so. That may or may not be a weakness, depending on what you want from a language. I do consider it a weakness, but I can see why others may not think so (see Rob Pike's "Less is More" talk).
I don't use Java, so I can't speak to the speed comparison. I found it significantly slower that C++, that's for sure, but still much faster than Python.
And consider what you do get with Go:
-
Lightning-fast build times.
-
Built-in, easy-to-use concurrency.
-
The interface mechanism is cool.
-
Garbage collection (yes, it slows things down, but it makes coding so much easier).
I used and enjoyed Go for a couple of years. I switched to Rust recently, and am cautiously excited about it. But I still think Go is cool, and would happily use it again.
Good summary of Rust. I love the language. D's great, but it needs to decide if it's garbage collected or not! Never looked at Nim, but isn't it basically a one-man project? Rust has the advantage of being backed by a major corporation (albeit an SJW-infested one).
I agree that Rust would survive in some form if Mozilla went under, but it would be a blow. The long-term financial viability of Mozilla is still Rust's biggest threat, IMO.