3 ms·
I wasn't saying someone should use Rust over Go because of Traits and other generic programming features. I was saying if you are evaluating Rust then Go proba
by jpgvm 12y ago
I wasn't saying someone should use Rust over Go because of Traits and other generic programming features.
I was saying if you are evaluating Rust then Go probably looks very feature light in comparison.
Same goes for programmers currently using Java/C# or even Haskell. Go is just a lot less featured than other high performance managed languages that are just as battle tested and just as fast.
This is not to say that it's not a good language or the correct tool for a job. Only that those programmers will be left wanting in many areas, generics only being one.
- NateDad 12y agoPeople who use Java and C# actually have a lot fewer reasons not to use go. The lack of a required runtime applies to both, better cross platform compatibility then C#, and lower memory overhead and faster startup than Java... You lose generics but you gain real value types and better concurrency primitives.
- deleted 12y ago[deleted]