HN about this 10 days ago:
Entropic – A Federated Package Manager for JavaScript
11–20 of 69 posts
Re: Entropic – A Federated Package Manager for JavaScript
#12If I visit their website without the www ( http://entropic.dev ), I get some curious JSON: {"server":"entropic","version":"0.0.1","message":"GCU Fate Amenable To Change","website":" https://www.entropic.dev" } Anyone know the significance of "GCU Fate Amenable To Change" ? I did Google it, but that didn't help much.
It's a reference to Iain Banks' culture universe - it's the name of one of the (sentient) ships.
Re: Entropic – A Federated Package Manager for JavaScript
#13I don't believe yet another package manager is going to fix anything, more likely it'll take years to reach maturity, will be riddled with bugs until then, and have some serious fundamental issues on its own that will be revealed down the path, if it ever gains popularity. Don't fix it if it aint broke should be a motto for more developers. Settling for good enough prevents second system effects and retards immaturit…
Most JavaScript-related threads I see on HN feature at least a handful of comments from people who will avow that e.g. the npm ecosystem is hot garbage. Seems to me that it is broke and needs fixed.
The main issue with it is that it's too good and successful, therefore it's too easy to publish whatever crap as your library or its dependencies.
That's not really a fault in the tool managing installation and publishing the library, its dependencies or managing the repository, providing the auditing system, script runner frontend and the other things npm does.
You could similarly argue github is hot garbage, because there are so many crappy projects hosted on it.
Re: Entropic – A Federated Package Manager for JavaScript
#14Earlier quoted context omitted.
Most JavaScript-related threads I see on HN feature at least a handful of comments from people who will avow that e.g. the npm ecosystem is hot garbage. Seems to me that it is broke and needs fixed.
The main issue with it is that it's too good and successful, therefore it's too easy to publish whatever crap as your library or its dependencies. That's not really a fault in the tool managing installation and publishing the library, its dependencies or managing the repository, providing the auditing system, script runner frontend and the other things npm does. You could similarly argue github is hot garbage, becaus…
It is the fault of the tool though if previous versions of a package are mutable, indeed deletable.
Re: Entropic – A Federated Package Manager for JavaScript
#15Earlier quoted context omitted.
The main issue with it is that it's too good and successful, therefore it's too easy to publish whatever crap as your library or its dependencies. That's not really a fault in the tool managing installation and publishing the library, its dependencies or managing the repository, providing the auditing system, script runner frontend and the other things npm does. You could similarly argue github is hot garbage, becaus…
It is the fault of the tool though if previous versions of a package are mutable, indeed deletable.
That's a fault of npm - _the registry_'s policies, not of the package manager. You could do the same with most other popular package managers if you have control over the registry.
Re: Entropic – A Federated Package Manager for JavaScript
#16Feels like there's a piece of the story missing: "There was one individual who planned though and didn’t give their viral software away for free." Who was that?
Isaac Z. Schlueter, the original creator of npm? I thought it was clear from the context but perhaps I'm missing something.
Re: Entropic – A Federated Package Manager for JavaScript
#17I am wondering, without having much knowledge about it, could a system like Ubuntu's package manager & registry (or any other Linux's distro) be suitable for JS?
Re: Entropic – A Federated Package Manager for JavaScript
#18Earlier quoted context omitted.
The main issue with it is that it's too good and successful, therefore it's too easy to publish whatever crap as your library or its dependencies. That's not really a fault in the tool managing installation and publishing the library, its dependencies or managing the repository, providing the auditing system, script runner frontend and the other things npm does. You could similarly argue github is hot garbage, becaus…
It is the fault of the tool though if previous versions of a package are mutable, indeed deletable.
It can and should be fixed in a backwards compatible way.
Re: Entropic – A Federated Package Manager for JavaScript
#19Earlier quoted context omitted.
It is the fault of the tool though if previous versions of a package are mutable, indeed deletable.
That's a fault of npm - _the registry_'s policies, not of the package manager. You could do the same with most other popular package managers if you have control over the registry.
Sounds like you're agreeing with the Entropic people: https://twitter.com/bitandbang/status/1134872073896169472
Their approach is to create a different kind of registries, and inevitably they need a new client that supports them.
Re: Entropic – A Federated Package Manager for JavaScript
#20The thing I don't get, is, I'm using Git repos as source for my packages for years now, why can't everyone do this?