4 ms·

What do you mean by "no solid dependency management"? Do you mean out of the box? This used to be true, but with glide and dep (https://github.com/golang/dep ht

by czbond 9y ago

What do you mean by "no solid dependency management"? Do you mean out of the box? This used to be true, but with glide and dep (https://github.com/golang/dep https://github.com/golang/dep) it seems to. It is not npm or bundler - but progressing.

chisleu 9y ago
Yes, go decided to wait to let the various competing systems duke it out in much the same way that node.js left it out for a while. I use git as my dependency management. I pull a specific version of a golang dependency and put it into my private git repository. Then i don't have to worry about someone's github getting hacked, repositories getting deleted, etc... Those problems have all happened with npm and github in the node ecosystem. Go solves these problems by allowing you to decide on how to manage your dependencies.
- iends 9y ago
  This is no longer true. The core team proposed vgo a few weeks ago, after the majority of the community solidified around godep.
- Keats 9y ago
  Do you also fork all their dependencies and subdependencies and fix the path in all of them? Otherwise you are still at the mercy of account/repo renames or deletions
andreygrehov 9y ago
They are going to be deprecated. See https://research.swtch.com/vgo https://research.swtch.com/vgo
- jerf 9y ago
  But in a nominally reverse compatible way, and nobody can really force you to stop using dep if that's what you do.
kbenson 9y ago
> It is not npm or bundler - but progressing. I assume NPM has gotten a lot better in the last few years if it's being used as example of something to strive towards. Every time I have to mess with the Node ecosystem, it really makes me question the direction I'm heading with the research or project I'm working on, just by the haphazard way modules seem to be used and dealt with on both the dependency level and at the repository/packager level. The last time was a couple months back with Reasonml. Reason seemed (and still seems) really cool, but ultimately I wasn't willing to put up with the umpteen layers of indirection just to compile to JS.[1] 1: I know there's an Ocaml compiler as well, but it didn't easily support some of the use cases I was looking at.
- bbatha 9y ago
  > I assume NPM has gotten a lot better in the last few years if it's being used as example of something to strive towards. Make sure that you are evaluating the tool not how the community uses the tool or npmjs.com runs the registry.
  - tonyarkles 9y ago
    They're pretty inseparable. If npm is great, and the community and default registry are terrible, I'm still not going to want to use the tool if I don't absolutely have to.
Cyph0n 9y ago
I was using one of the points raised in the linked article to refute OP's point about "personal opinions" in the context of critiquing programming languages in general.
- czbond 9y ago
  You did. My mistake, I guess the point you were making didn't register.

by czbond 9y ago

chisleu 9y ago

Yes, go decided to wait to let the various competing systems duke it out in much the same way that node.js left it out for a while. I use git as my dependency management. I pull a specific version of a golang dependency and put it into my private git repository. Then i don't have to worry about someone's github getting hacked, repositories getting deleted, etc... Those problems have all happened with npm and github in the node ecosystem. Go solves these problems by allowing you to decide on how to manage your dependencies.

iends 9y ago
This is no longer true. The core team proposed vgo a few weeks ago, after the majority of the community solidified around godep.
Keats 9y ago
Do you also fork all their dependencies and subdependencies and fix the path in all of them? Otherwise you are still at the mercy of account/repo renames or deletions

andreygrehov 9y ago

They are going to be deprecated. See https://research.swtch.com/vgo https://research.swtch.com/vgo

jerf 9y ago
But in a nominally reverse compatible way, and nobody can really force you to stop using dep if that's what you do.

kbenson 9y ago

> It is not npm or bundler - but progressing. I assume NPM has gotten a lot better in the last few years if it's being used as example of something to strive towards. Every time I have to mess with the Node ecosystem, it really makes me question the direction I'm heading with the research or project I'm working on, just by the haphazard way modules seem to be used and dealt with on both the dependency level and at the repository/packager level. The last time was a couple months back with Reasonml. Reason seemed (and still seems) really cool, but ultimately I wasn't willing to put up with the umpteen layers of indirection just to compile to JS.[1] 1: I know there's an Ocaml compiler as well, but it didn't easily support some of the use cases I was looking at.

bbatha 9y ago
> I assume NPM has gotten a lot better in the last few years if it's being used as example of something to strive towards. Make sure that you are evaluating the tool not how the community uses the tool or npmjs.com runs the registry.
- tonyarkles 9y ago
  They're pretty inseparable. If npm is great, and the community and default registry are terrible, I'm still not going to want to use the tool if I don't absolutely have to.

Cyph0n 9y ago

I was using one of the points raised in the linked article to refute OP's point about "personal opinions" in the context of critiquing programming languages in general.

czbond 9y ago
You did. My mistake, I guess the point you were making didn't register.