4 ms·
> 1. Go uses capitalization to determine identifier visibility This complaint sounds like it's more about Go doing it differently than the language the writer
by baby 9y ago
> 1. Go uses capitalization to determine identifier visibility
This complaint sounds like it's more about Go doing it differently than the language the writer is used to.
> 2. Structs do not explicitly declare which interfaces they implement.
It sounds like this is probably to have structs that will please several interfaces, but I can't find a good example of that in the go std lib. Anyone?
> 3. It’s far too easy to forget to check errors
use a linter that warns you when you do this
> 4. if I name my source file i_love_linux.go
That's actually a pretty cool and light way to implement something for multiple platforms I thought...
> If I accidentally name a function init()
Go has so few forbidden keywords that I can't really appreciate this complaint.
> In Java [...]. Sometimes I find it hard to read Go
So Java is easier to read than Go? Come on!
> I see no good argument for omitting this [ternary] operator
Less ways to write the same thing. Improve code readability.
> Import versioning and vendoring is terrible
I would say Go has the best standard tools. It's not perfect yes, but it's better than other languages.
> No generics
that's a good thing
This post really feels weird when in another thread of HN's FP you have people arguing that a 35 LOC package is a good thing in js.