Live data from Hacker News

Entropic: A federated package registry for anything

github.com

1–10 of 13 posts

Re: Entropic: A federated package registry for anything

#3
post #2

Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?

Wait, is that common? I’ve not seen anyone doing that before. A cursory search shows a tool that takes a yarn.lock file and turns it into a Nix expression, but that’s all I can see.

Re: Entropic: A federated package registry for anything

#4
post #2

Hmm, 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?

Re: Entropic: A federated package registry for anything

#7
post #2

Hmm, why is this a good thing compared to just using Nix / nix-pkgs to manage JS packages?

Similarly in my experience apt/deb packaging should be considered for this. There's already node packages in Debian/Ubuntu, to look at examples, it's well documented, tried and tested, they can be signed, and it's straightforward to setup a repo which is completely static, so can be put in S3 or any static server, there's apt-transport-tor, for working over tor, there's apt-transport-s3 for working with private S3 buckets. OK there's some versioning quirks (I've used both launchpad and reprepro) such as tying it to a release version (buster, xenial, bionic, etc..) and having only one version of a package available per release in the case of reprepro, but in my experience it was easy to setup and maintain. Also the penetration of the format means you can consume it, in one form or another on Linux, WSL, ChromeOS, Docker, K8S, etc.

Re: Entropic: A federated package registry for anything

#9
Previous discussion: https://news.ycombinator.com/item?id=20076814

The 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

#10
post #2

Hmm, 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?

nixpkgs top-level only accepts full applications, not libraries, but there is a documented procedure for adding applications to nixpkgs: https://nixos.org/nixpkgs/manual/#node.js-packages
Post reply on HN