@Linux sorry, you aren't making sense. You want to side step nix store with flatpaks basically and "not compile stuff from source", where the whole premise is reproducible builds from source based on hashed arguments to build functions.

Furthermore, it's delusional that NixOS can be easy. I use BSD / Linux as a daily driver since I was 14, switched to NixOS from Arch in 2013, I loved NixOS when stuff worked, but when it doesn't work, you need to write a fucking dissertation on fixing it. Or ask nice people from the community for help (and then write a dissertation).

NixOS will never be simple.

The only way to make it simple is heroic effort of people like the #nvix guy: assemble opinionated expressions, which you can eval to get configured software, deterministically.

Unsurprisingly, integrating stuff like #nvix is easier when there is a clear and uniform evaluation mechanism. That's another way how flakes help adoption 🤷‍♀️

I get it, you are used to stuff you are used to, but I'm not only not seeing a valid argument against using flakes for configuring the system, I'm also yet to see a coherent statement that could pass for an informed opinion.

Sorry for being harsh, but like... If you want NixOS to be simpler, you should be first in line for flakes for system configuration. 🤔

@jakehamilton how do you install plug-ins for #neovim that aren't in #nixvim btw?

I need #notion plug-in because people at work delude themselves that they will manage to keep an up-to-date notion knowledge base, but I'm using #nvix, which is a wrapper around #nixvim, so I'd like to gauge roughly how much time should I allocate to figuring out how to install a plugin.