cardano-sl VS nixpkgs

The daily developments were reduced by August but resumed vigorously in September. The whole of September was a busy month for developers as the daily submission rates for most coins were very high. At this time, ETH, DOT, and ADA were the leader as SOL followed closely behind. It was not till towards Mid-October that the daily developments reduced.

So, uh, the two things the blog post covers are actively awful practices. Let's look at Logging. Logging boils down to ServantLogConfig, which carries a function Text -> IO (). This is bad. Text is not a great type for logging, since it's relatively slow and encodings aren't guaranteed to be sensible (cf this bug where logging to a file was broken based on environment encoding). You want something like LogStr from fast-logger, or even a ByteString.Builder or Text.Builder even.

oops I want my Daedalus wallet (actually very surprising it's not there as Cardano uses Nix). Meanwhile this packaging request has been Open since 2017.

Otherwise you can use the following instructions for adding the caches to your local Nix install: https://github.com/input-output-hk/cardano-sl/blob/master/docs/nix.md#binary-cache

For what it's worth, coincheckup is tracking https://github.com/input-output-hk/cardano-sl which is the old repo from before they split up a lot of the infrastructure into their own repos.

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...