4 ms·
What clusterfuck? The current version module system works if people can maintain compat. If not, nothing will save you.
by wbl 6y ago
What clusterfuck? The current version module system works if people can maintain compat. If not, nothing will save you.
- free_rms 6y agoIt took them like a decade to get there though, all the while telling the entire non-Google world that they must be doing something wrong if they want versioning for their dependencies.
- eikenberry 6y agoThe problem was that there were no dependency solutions at the time that really nailed it. Most systems used something similar to Ruby's Bundler system, which was terrible to work with. Personally I like that the Go team is patient and takes the long view when adding features to the core tool set and language.
- wbl 6y agoThat was never the position and lots of third party tools sprung up to make things work once the vendor folder was added in Go 1.5. That was three years after the language was released.
- deleted 6y ago[deleted]
- kortilla 6y agoThe current version module system is built on a decade of anguish that finally toppled over and forced some serious interest. The problem is that it was a complete non-issue for Google because of the monorepo so the golang devs employed by Google severely downplayed the problem.