waymonad VS nixpkgs

I am personally waiting for Waymonad. https://github.com/waymonad/waymonad

It takes time, but the teams behind wlroots etc are doing good work to make sure that wms managed by smaller teams can exist. There are even clones for your specific wm on wayland. See https://github.com/waymonad/waymonad

In addition, there was the last commit in 2019. Thus, it can be assumed that the project is dead and therefore nothing will change on the current state. And according to https://github.com/waymonad/waymonad/issues/44, there are probably not enough people who would actively participate in a fork.

Ideally xmonad would be ported/xmonad devs would be working on waymonad, but I doubt it will happen. Waymonad seems to be abandoned.

Nice to see Qtile on Wayland. But I'm personally waiting for xmonad on Wayland.

https://github.com/waymonad/waymonad

I wouldn't count on it, as Waymonad has not seen active development since 2019 and the Haskell bindings to wlroots have not been updated since 2019 as well. There is a fork, but it has not been active since September 2021. Also, it was based on wlroots, not sway.

That's what the XMonad fans are using: https://github.com/waymonad/waymonad lets you write your Wayland compositor in Haskell, is analogy to the way XMonad lets you write your X window manager in Haskell.

Unfortunately it was abandoned https://github.com/waymonad/waymonad/issues/44

regarding keeping an interest, waymonad has been dead for something like two and a half years but according to startrack it's still getting people giving him stars so i don't think you should worry about it.

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