It is indeed kind of hard to do it here! hehe
First the things I like about both is the fact that at the end of the day, no matter which one you're using you can always end up exposing the
vendor directory therefore letting your users simply use your code without having to care about your choice for dependency management.
On the other side dep is not integrated into the go tooling as much as modules (for reasons that belong more to political rather than technical conversations). This means that eventually everyone will be able to use modules natively without having to have an extra tool ... and we know programmers are lazy!
So yeah, I'd say modules and dep are both solutions to the same problem, but given the fact that modules is already integrated with the official Go tooling I do not think dep will be popular for much longer.
And that makes me a bit sad, because the team of gophers behind dep is amazing! Great people and great coders. The show must go on, as they say.
Reply to this…