Entropic – A Federated Package Manager for JavaScript
1–10 of 69 posts
Re: Entropic – A Federated Package Manager for JavaScript
#2I 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 immaturity in the form new "trendy" products that over-promise and under-deliver solutions.
Nothing is perfect, but replacing something from scratch because of some mostly irrelevant issues that would be better handled by improving the standard solution usually just causes more issues than it solves.
Re: Entropic – A Federated Package Manager for JavaScript
#3I 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…
> mostly irrelevant issues
95% of the talk is about why those issues aren't irrelevant. Care to respond to those?
Re: Entropic – A Federated Package Manager for JavaScript
#4What about Yarn?
Re: Entropic – A Federated Package Manager for JavaScript
#5Feels 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?
Re: Entropic – A Federated Package Manager for JavaScript
#6Here's the actual talk on youtube: https://www.youtube.com/watch?v=MO8hZlgK5zc
Re: Entropic – A Federated Package Manager for JavaScript
#7I 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.
Re: Entropic – A Federated Package Manager for JavaScript
#8What about Yarn?
As a Facebook-managed project, Yarn's focus is probably more on FB's needs: fast, repeatable builds from centralized package repositories on their own private network.
There's ample room for a federated community project in this space, IMHO. I'd certainly be eager to kiss npm goodbye.
Re: Entropic – A Federated Package Manager for JavaScript
#9If 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.
Re: Entropic – A Federated Package Manager for JavaScript
#10It is interesting to see the package management approach Deno (Ryan Dahl’s new project) is taking. It has stated as an explicit goal to make the package manager part of the same deno runtime. It tries to achieve this by supporting a native webstandard for modules out of the box. The approach seems to be partially inspired by the go 1.14 module system.