34 ms·
Except for "static binaries" (which isn't clear what benefits you desire out of them), java has all those things. The other choices are certainly there.
by grogers 12y ago
Except for "static binaries" (which isn't clear what benefits you desire out of them), java has all those things.
The other choices are certainly there.
- Alphasite_ 12y agoAnd even Java is getting that.
- zzzcpan 12y agoToo late. Also Java is not as easy to learn and to use as Golang.
- waps 12y agoToo bad you can't unlearn functional programming. Or generic programming. Or algebraic datatypes. Or having actual useful datatypes. Or ... Just the basic thing of sorting a list containing a struct. And the suggested solution by the Go team is a 50 line program. WTF. They actually claim the err = function(); if err != nil {}. This is the reason I originally left C. And those criticisms really apply to Go as well. Firstly nobody sanely checks those errors, often outright ignoring them. Second when they do, they always just pass the error up (in other words: manually implementing exceptions), or worse, they panic on the error (meaning you cannot trust external libraries won't panic on you, negating the single advantage that leaving out exceptions had). Even if you do check those errors they interrupt the train of thought you have. Imagine someone telling you how to open a door in Go : first, put your hand on the handle. If you don't have a hand then go to the hospital. If there is no hospital near you then go to the car. If there is no car then check for a bike. If the door is locked ... wait what was I doing ? Thirdly functions that might return a variable or might not ... the official Go team's advice is use a pointer. Sigh. The amount of times I've seen people commit Go code into my program that doesn't check for nil-ness ... Grrrr. If you don't mind living in the dark ages, then yes, Go is great.
- NateDad 12y agoExcept for "reasonable memory usage".