3 ms·
I don't see much success to begin with. Thought they did things in the article right. Having formal spec, and focusing on code stability is important, and put
by baybal2 7y ago
I don't see much success to begin with.
Thought they did things in the article right.
Having formal spec, and focusing on code stability is important, and puts them apart from 9 out of 10 of every new programming languages, but that is only one item on the long "not suck" list.
The lack of proper package management at the start left too much of a bad aftertaste.
I believe they must have knew that shipping go with git as a makeshift package manager was a bad idea, but for some reason did it anyway. I think this alone turned away half of early adopters.
Then golang went through a long epopeia of making the package ecosystem work outside of a single company deployment, and lost a lot of developers along the way again.