Entropic: A federated package registry for anything
1–10 of 13 posts
Re: Entropic: A federated package registry for anything
#2Re: Entropic: A federated package registry for anything
#3Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?
Re: Entropic: A federated package registry for anything
#4Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?
I tried with yarn2nix and quickly decided to just use regular nom install every time.
Can you share your experience?
Re: Entropic: A federated package registry for anything
#5Re: Entropic: A federated package registry for anything
#6Re: Entropic: A federated package registry for anything
#7Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?
Re: Entropic: A federated package registry for anything
#8Why is this posted here again? Is it usable now?
Re: Entropic: A federated package registry for anything
#9The idea of a federated package registry is good: it tries to avoid centralization and control of a language ecosystem by a private company (like it happened with NPM).
However, I think it can easily be gamed, the same way Git was gamed by GitHub. I do wonder what prevents any of the big companies, for example, Microsoft through Github, to host an instance of Entropic, and adding too-good-to-be-true features on top. These could be automatic vulnerability alerts, detailed metrics, integration with code completion services, but only if you use their instance, and could serve to convince anyone to host mainly on Github’s instance. Then they roll their own CLI that supports Github-only features, and then they close API access to third party clients. The Apache 2 license would allow all of this, without problems.
This has happened before with XMPP (Google Talk, Facebook Chat), IRC (Slack, Discord) and SMTP (Gmail). I think we’ll need more than federated protocols to solve the problem of VC-backed companies, but at least this is a start.
Re: Entropic: A federated package registry for anything
#10Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?
I tried doing this for golang with dep2nix and vgo2nix and it is quite hard, but I succeeded. I tried with yarn2nix and quickly decided to just use regular nom install every time. Can you share your experience?