pldb VS nixpkgs

pldb.pub

How does it compare to https://pldb.com ?

Good Catch!

Updated here: https://github.com/breck7/pldb/commit/312d5dab32fda3782e8466...

We had this but the title was set to "xtclang". Just fixed (https://github.com/breck7/pldb/commit/1673baa00e5d44e7fd8ac9564480d6301063aa25). Thank you!

Don't have time to install but I would pay $10 in NEAR coin if you can email or post the results of my repos to me ([email protected]):

https://github.com/breck7/jtree and https://github.com/breck7/pldb

Interesting! I built a new system from the ground up for this sort of thing called TreeBase. It powers PLDB.com (https://github.com/breck7/pldb).

I don't have much experience using GraphQL. Is it a fun language to use? I wonder if we should provide a GraphQL API to PLDB.

Ok. Thank you! I just swapped with your code: https://github.com/breck7/pldb/commit/42d5562583e18fd141b979b16d30a8a4d7c5619c

Cofounder of https://musicofapeople.com/ pldb.com scroll.pub (and more coming soon like cancerdb.com and an exciting new reddit competitor)

Programming Language Database

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...