3 ms·
How has go not solved this when it's had npm as an example for 6 years?
by billytetrud 9y ago
How has go not solved this when it's had npm as an example for 6 years?
- ovao 9y agoIt’s explained in the post. To summarize: the Go team felt it would be best if users developed the tooling to solve the problem rather than having an official solution. This resulted in too many solutions, which is itself a non-solution. Pretty clearly this was a mistake by the Go team, and the blog post says as much.