vivarium
nixpkgs
vivarium | nixpkgs | |
---|---|---|
5 | 975 | |
347 | 15,753 | |
- | 2.8% | |
2.8 | 10.0 | |
8 months ago | 3 days ago | |
C | Nix | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vivarium
-
With rise of wayland, are simpler window managers dying?
Take a look to Vivarium It is more recent it worked decently and it is remakably easy to config.
-
I am looking for a wayland based tiling window manager which is close to dwm/xmonad, which one would you recommend?
I wrote Vivarium specifically to behave like my old xmonad setup, although it isn't at all like xmonad internally. It's configurable in C.
-
XMonad – The Automated Tiling WM
Since various people are asking about xmonad-like tiling in wayland:
I wrote Vivarium[0] specifically to be a wayland compositor that behaves exactly like my (fairly simple) xmonad config, but it's a relatively new/unstable compositor and nothing like xmonad internally.
River[1] has a fantastic tiling model via user-provided executables, which makes it very flexible and probably a good fit for many people wanting something xmonad-like.
Waymonad[2] exists as a direct xmonad-like compositor, but I think development has been basically stalled for a long time. Sometimes there's discussion about reviving it though.
[0] https://github.com/inclement/vivarium
[1] https://github.com/ifreund/river
[2] https://github.com/waymonad/waymonad
-
Recommended Compositors
Vivarium has xwayland as an option, enabled by default.
-
xorg sucks, use swc
https://github.com/inclement/vivarium.git and https://github.com/djpohly/dwl.git are also great projects in the same vein.
nixpkgs
-
Nix: The Breaking Point
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...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
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,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
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...
-
The xz attack shell script
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...
-
Debian Git Monorepo
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
-
From xz to ibus: more questionable tarballs
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...
What are some alternatives?
river - [mirror] A dynamic tiling Wayland compositor
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
waymonad - A wayland compositor based on ideas from and inspired by xmonad
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
velox - velox window manager
git-lfs - Git extension for versioning large files
waymonad - A wayland compositor based on ideas from and inspired by xmonad
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
qtile - :cookie: A full-featured, hackable tiling window manager written and configured in Python (X11 + Wayland)
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
spectrwm - A small dynamic tiling window manager for X11.
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.