Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
AppImageKit
Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
What I mean by that is: I have all my configs tracked in a git repository. It is faster to hack something together on a different distro, but if I get it working on nixos and add it to my configuration repository, it wont magically break. It is reproducible and versioned, with rollbacks to any version always possible. You will have to decide if that is worth the effort for yourself, I personally have no problem investing a bit more time on the initial configuration of a service or a custom module knowing it is a piece of configuration I can always reliably reuse and build upon. Just my two cents.
nickel addresses the type system issue. It is unclear what the roadmap is for integration into NixOS, but since it is made by tweag/Eelco and has Nix as a primary use case, there is definitely reason to hope for a cleaned up language.
Here's my setup with flakes and home-manager if anyone is interested: https://github.com/erikbackman/nixos-config
Would it make sense to design nix around the AppImage standard? The full package in a single cross-platform binary, no external dependencies, no patching just to get it to work in NixOS. It seems like all Linuxes should be moving in that direction, tbh.