nyxt-init.lisp VS nixpkgs

=> there little things that I usually do in a terminal that I now do in a browser. Nyxt gives me a nice fuzzy completion prompt for any list of strings, it gives me the possibility to print rich text, etc.

There's something I didn't manage to do yet but am wanting very much, is to be able to react to Webkit web events. Last time I checked they were not exposed on Nyxt, only on the C side. I would react to button clicks, I would add new buttons on the page and react to them. That'd be awesome.

All this is written in Common Lisp, that is strange at first (rest assured, you're normal), but it's a great language with a long history of industry use, so it's solid and it's good to have it on my toolbet. I am now lauching new services in CL rather than in Python, that is so slow, unstable and error prone.

my snippets: https://github.com/vindarel/next-init.lisp/ (outdated, I didn't follow the latest changes)

other great config: https://github.com/tviti/next-cfg/ and https://github.com/tviti/next-notebook (interface with Jupyter)

This will drop you into a shell where `tracexec` is installed.

[1]: https://github.com/NixOS/nixpkgs/pull/310158

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