wlroots VS nixpkgs

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.

gamescope use wlroots

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