3 ms·
Yet another problem the go team refuses to see. Either the go team says "not our problem" then people are stuck with doing things multiple and incompatibles way
by aikah 12y ago
Yet another problem the go team refuses to see. Either the go team says "not our problem" then people are stuck with doing things multiple and incompatibles ways , or the go team says "we already solve the problem, vendoring" and the go team doesnt understand the problem at first place. That's the recurrent pattern with the Go team. Everything cannot be dealt with in userland, or you'll end up with fragmentation. And No , vendoring doesn't solve the problem.
- davecheney 12y agoHonest question: Why does vendoring not solve the problem ?
- kungfooguru 12y agoI bet it works great for Google or anyone else who keeps everything in one big repo and isn't developing open source applications.
- deleted 12y ago[deleted]
- Titanous 12y agoVendoring works great for us, we keep everything in one big repo and it's open source. The problem is that the current tooling for managing this is horrible.
- nulltype 12y agoWhat is horrible about managing it? The biggest problem I encountered with vendoring is getting rid of git submodules.
- Titanous 12y agoWe currently use godep, and it breaks very easily due to tags and differing architectures and OSes (among other things). In addition to being unreliable, it's pretty slow. I'm not aware of any other tools that do import rewriting+vendoring and work better than godep.
- nothrabannosir 12y agoBut... almost every sentence in that comment is "not applicable" at best. * the major players all solve this specific problem outside the lang core * Dave Cheney is so involved with the project, you could easily consider him part of the "go team." Both in contributions and community pull. * This very article is not about a problem, it's about a solution. It's literally Dave Cheney saying: wow, look at this important problem, and look at all the reasons why it's important. Here is a solution and all its pros and cons. Regardless of how you feel, the timing of your comment simply could not have been further off. * More generally: Go is one of the most batteries-included languages I know. From the stdlib to the tooling (which is still part of the official release), it's all in there. When did you last try to create platform and architecture independent binaries without any prior knowledge in, I don't know; C? Even Python? I really want to like this comment, believe me I do. But it is so out of tune with the article, I can't. This article is almost literally about the opposite of everything you just wrote.
- LamaOfRuin 12y ago> * Dave Cheney is so involved with the project, you could easily consider him part of the "go team." Both in contributions and community pull. Wait, is he not officially part of the go team?
- PopsiclePete 12y agoBy "Go team", do you mean "Salary paid by Google"? Then no, I believe he works for Canonical...but he's pretty "core" in all other aspects.