4 ms·

I'm a huge fan of Go, and not a fan of dependencies at all, so I tend to vendor everything. Go mod just looks like a total mess from the outside. To be honest

I'm a huge fan of Go, and not a fan of dependencies at all, so I tend to vendor everything. Go mod just looks like a total mess from the outside. To be honest I (like most gophers I've talked to) never really understood why dep wasn't adopted as the official solution for this. I'm resisting converting my projects to modules until there's a clear and definite advantage to it. So far, none.

Thaxll 6y ago
Dep was crap and ultra slow.
dewey 6y ago
> I'm resisting converting my projects to modules until there's a clear and definite advantage to it. So far, none. Go modules are not going to go away so what benefits will waiting as long as possible give you? I'm not a big fan but it's fine in day to day life and the most common issue for me is that some indirect dependency is having issues which is usually solved with some "replace" lines in the go mod file. Not ideal but also not too annoying.
- marcus_holmes 6y ago
  Well the main benefit is not wasting time dealing with it ;) I know I'll have to do it one day. Hopefully that day will be after they've brought more sanity to it.
CamouflagedKiwi 6y ago
I tried dep for a project of mine and could never even get it to the point of doing anything useful. Conversely go mod took about three minutes to migrate to and was super straightforward. I am very happy that they did not adopt dep, it was in no way ready (and I don't think it was going to significantly improve given more time).
- marcus_holmes 6y ago
  True, there were problems with it, it wasn't perfect by any means. I guess the main complaint at the time was that it appeared to be "not invented here" syndrome. The community was converging on dep, and then the Go team decided to do something different, for reasons that weren't completely clear. It kinda rammed home the reality that Go is not a community project, it's a Google product controlled by a small team. That definitely has benefits and good points, but it doesn't match everyone's expectations.

Thaxll 6y ago

Dep was crap and ultra slow.

dewey 6y ago

> I'm resisting converting my projects to modules until there's a clear and definite advantage to it. So far, none. Go modules are not going to go away so what benefits will waiting as long as possible give you? I'm not a big fan but it's fine in day to day life and the most common issue for me is that some indirect dependency is having issues which is usually solved with some "replace" lines in the go mod file. Not ideal but also not too annoying.

marcus_holmes 6y ago
Well the main benefit is not wasting time dealing with it ;) I know I'll have to do it one day. Hopefully that day will be after they've brought more sanity to it.

CamouflagedKiwi 6y ago

I tried dep for a project of mine and could never even get it to the point of doing anything useful. Conversely go mod took about three minutes to migrate to and was super straightforward. I am very happy that they did not adopt dep, it was in no way ready (and I don't think it was going to significantly improve given more time).

marcus_holmes 6y ago
True, there were problems with it, it wasn't perfect by any means. I guess the main complaint at the time was that it appeared to be "not invented here" syndrome. The community was converging on dep, and then the Go team decided to do something different, for reasons that weren't completely clear. It kinda rammed home the reality that Go is not a community project, it's a Google product controlled by a small team. That definitely has benefits and good points, but it doesn't match everyone's expectations.