3 ms·
True, but that's what people using Go have been doing for years without complaining much, so I guess it works fine for most workload. And before npm fixed thin
by littlestymaar 7y ago
True, but that's what people using Go have been doing for years without complaining much, so I guess it works fine for most workload.
And before npm fixed things after the left-pad incident, the npm builds where not reproducible either (as demonstrated by the said left-pad incident).
- Bahamut 7y agoDependency management is one of the biggest complaints I have seen around Go - I don't think this is accurate.
- littlestymaar 7y agoI don't like it either, but it still works well enough for many people.
- thayne 7y agoThat is one of the things I hate about go. Right up there with lack of generics and boilerplate error handling.
- pawalt 7y agoThis hasn't been a thing in Go for a long time. Go dep and now go modules fix this.
- qudat 7y ago> True, but that's what people using Go have been doing for years without complaining much, so I guess it works fine for most workload. I hate to break it to you but dependency management has been a massive issue in golang until the devs formally adopted go mod. Only Google seemed okay with checking in their dependencies to version control. Everyone else was doing crazy hacks like https://labix.org/gopkg.in https://labix.org/gopkg.in
- Rapzid 7y agoIt created a hugely fractured open source ecosystem as well.
- dgellow 7y agoThe vendoring has never been the issue though.
- littlestymaar 7y agoI have only used Go once at work, and I actually dislike most of it (and dependency management was one of the annoying things with Go), nonetheless it is has never been a show stopper and there have been thousands of developers using it when vendoring was the only option.
- z3t4 7y agoChecking in dependencies to version control is the sane option. Then you can more easily see what's updated and track regressions. Some people like to refactor their code any time there is a syntax sugar added to the language - often adding a few bugs while doing it, which is a PITA, but version control is still better then no version control. You will ask, what about adding the OS to your SCM too, yeh why not have the full software stack. But you can generally draw a line between strong abstraction layers: Hardware | Kernel | OS | runtime | your app. Some modules do have strong abstraction layers, but others are just pure functions which you could just as well copy into your own repo.
- christophilus 7y agoGo compiles to a static binary. It’s not downloading and running source on your production servers. Isn’t that the concern here?
- alienspaces 7y agoGo dependency management is quite good now with "go mod", plus your dependency tree isn't going to look anything like your typical JavaScript dependencies, otherwise you're doing it wrong..
- rplnt 7y ago> that's what people using Go have been doing for years without complaining I haven't seen anyone commit vendor and not complain about it. But now you finally don't have to commit vendor for reproducible builds. All you need is a module proxy. The "all you need" is not really meant seriously of course. And I personally prefer to not commit vendor and complain about it.