This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
We repurposed NPM to publish and distribute Go binaries for our internal CLI
21–30 of 65 posts
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#22This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
It saddens you that someone used a tool they already use instead of adding another thing to distribute a small binary?
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#23This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
I thought the same thing (Go binaries are so easy to distribute), but they do explain that their devs already have credentials for an internal NPM server, and they wanted to do this "without the need of distributing a new set of tokens or making the binary public". I don't think the trade-off is worth it, but at least it explains their motivation.
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#24This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
https://node-os.com/
Dang, I wish I could say I'm surprised, but I guess it was to be expected.
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#25This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
I thought the same thing (Go binaries are so easy to distribute), but they do explain that their devs already have credentials for an internal NPM server, and they wanted to do this "without the need of distributing a new set of tokens or making the binary public". I don't think the trade-off is worth it, but at least it explains their motivation.
In their particular case, what's the trade-off that's so terrible though? They already all have npm, they had a binary to distribute, and they distributed it.
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#26This just saddens me deeply. Of all the ways this could have been done and all the package managers they could have used they picked npm. I bet some day we'll have a Linux distro with npm as the system package manager here on HN.
It saddens you that someone used a tool they already use instead of adding another thing to distribute a small binary?
I guess my comment appears rude, which wasn't intended, I just find npm a troublesome piece of software that is passable as a package manager for the javascript ecosystem, but not a tool one solves problems with if there are viable alternatives.
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#27Next: Docker images!
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#28Earlier quoted context omitted.
It saddens you that someone used a tool they already use instead of adding another thing to distribute a small binary?
I guess my comment appears rude, which wasn't intended, I just find npm a troublesome piece of software that is passable as a package manager for the javascript ecosystem, but not a tool one solves problems with if there are viable alternatives.
why is it trouble? why can't they improve it even if its trouble?
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#29Earlier quoted context omitted.
It saddens you that someone used a tool they already use instead of adding another thing to distribute a small binary?
I guess my comment appears rude, which wasn't intended, I just find npm a troublesome piece of software that is passable as a package manager for the javascript ecosystem, but not a tool one solves problems with if there are viable alternatives.
[deleted]
Re: We repurposed NPM to publish and distribute Go binaries for our internal CLI
#30Earlier quoted context omitted.
It saddens you that someone used a tool they already use instead of adding another thing to distribute a small binary?
I guess my comment appears rude, which wasn't intended, I just find npm a troublesome piece of software that is passable as a package manager for the javascript ecosystem, but not a tool one solves problems with if there are viable alternatives.
When you have one thing to nail and already own a hammer, why go and buy another one? Even if it's not a good one, it's gonna do the job, and be the least trouble.