quine-relay VS nixpkgs

If there were more languages, then it'd be `console.log("System.out.println({python_source})")`, etc. The problem then becomes quoting and escaping inner quotes. I managed to avoid the problem by using both single and double quotes, and relying on Python's `repr` also giving valid JS strings, but if I had to add one more language I'd have problems.

I still think the Quine Relay is a tour de force, but for different reasons. It's not 128 quines in different languages, but an incredibly robust system for quoting and escaping strings in 128 different languages.

[1] https://github.com/mame/quine-relay/blob/master/src/code-gen...

One of the most impressive works I've seen: https://github.com/mame/quine-relay

"Quine" is a type of program, when executed, will output itself (it's actually it's source code). It's very hard to write one. And this guy wrote a loop quine. It supposed to work like this: * A program in language A output a program in language B * The program in language B output a program in language C * The program in language C output the same program in language A which we started with

Or a Quine relay.

Why use a couple of languages, when you can use 128 of them simultaneously? https://github.com/mame/quine-relay

Quine relay [1] is to this day the most "I will never understand this" brainfuck project I have ever seen.

[1] https://github.com/mame/quine-relay

Go look at a programming quine and tell me it isn't art.

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