Re:The Hard Part of Learning a Language
by arendtio on Saturday May 30, 2020 @07:31AM
(#23360384)
I think this is a point where Go is very good at and JavaScript sucks pretty hard. Mostly because Go brings many things by default and JavaScript has such a high rate at which new tools become mainstream/obsolete and so many options to choose from and combine with.
[ Parent
| on HN ]
Re:The Hard Part of Learning a Language
by loudlambda on Saturday May 30, 2020 @11:32AM
(#23361833)
I found the opposite to be true. With javascript I never saw the package.json not work for the other developers on the team; with go, half of my team can't successfully update vendoring for no apparent reason.
Commands frequently error with messages that are completely worthless.
Go seems to have made up it's own path syntax with things like "...", and commands like "go test foo/bar" will fail with an error message that gives no clue as to the problem, but work fine with "go test ./foo/bar". Why?
What's the command to see if any of my dependencies have a CVE against them? Oh, there isn't one. What's the command to prompt me to pull in a new version of my dependencies? Oh, there isn't one.
This is a language that has made some promise about backwards comparability, but every release seems to break how things are built, and you have to fiddle with bizarre environment variables like GO111MODULE to find the incantation to make things happy again.
Re:The Hard Part of Learning a Language
by mellosouls on Saturday May 30, 2020 @09:16AM
(#23360945)
Give Go another 15 years to catch up with JavaScript's current maturity and see where we are then with its ecosystem.
Re:The Hard Part of Learning a Language
by moreaccountspls on Saturday May 30, 2020 @11:46AM
(#23361932)
I mean, Node and Go were released within 6 months of each other. When jquery was the dominant tool in the ecosystem, there wasn't nearly the level of breakage that there is now.