3 ms·
Do you have proof that the Go team has not looked at any other dependency management approaches or considered ones from other languages?
by jjuel 9y ago
Do you have proof that the Go team has not looked at any other dependency management approaches or considered ones from other languages?
- stouset 9y agoObviously I don’t, but the available evidence — to me, anyway — points to this being a cultural reality in the golang ecosystem. I left the language years ago, but the steady stream of articles of the form “Why go doesn’t need $x” followed by innumerable comments, articles, and blog posts by people struggling with the lack of $x, followed by the go core team (due to the completely foreseeable consequences of not having $x) begrudgingly adopting $y, which is supposed to (but doesn’t actually) obviate the need for $x… I’ve reached my own conclusions, and I’m finding more and more people who are leaving the ecosystem with those same conclusions. I believe that Go excellently solves problems that Google has. I don’t believe it solves many problems that most other users have, even though it might seem like it at the outset.
- pjmlp 9y agoWait until they finally cave in to generics being one of the top requests on Go surveys and bring something to Go following that same design process.