couldn’t you always just run a Linux VM at near-native speed, and get the benefits of both?

The obvious downside is that Linux is no longer the host OS. MacOS or Windows would be closed source code managing your hardware. And any VM could only be as fast as the host OS allows it to be.

It’s been this way for at least a decade.

I’m not in the market, but I’ve actually had similar thoughts of building a project on top of NixOS that’s focused on self-hosting for homes and small businesses. I recently deployed my own router/server on a BeeLink mini PC and instead of using something like OpenWRT, I used NixOS, systemd-networkd, nftables, etc.

DM me if you want to discuss more. I think the idea has potential and I might be interested in helping if you can get the business model right (even if it just ends up being some FOSS thing).

Stop using Brave, people.

The only correct answer is to be consistent with the code base you’re working in or the language’s conventions. If neither of these conventions exist, then someone has already failed you.

You can’t configure an immutable distro by a sequence of mutations.

Isn’t that literally how ostree works?

NixOS

You should say “unstable channel”. It’s literally just a rolling release that pulls from the nixpkgs master branch. So it’s only as stable as it needs to be to pass the Hydra CI tests.

And if you get to a working version, you can pin that as a Nix flake to avoid anything breaking until the next time you nix flake update.

It’s so ironic how many downvotes this is getting in the context of this thread.

This reminds me of the apparent gnome-keyring security hole. It’s mentioned in the first section of the arch wiki entry: https://wiki.archlinux.org/title/GNOME/Keyring

Any application can read keyring entries of the other apps. So it’s pretty trivial to make a targeted attack on someone’s account if you can get them to run an executable on their machine.

There’s also the Wayblue family of Wayland distros, based on Ublue.

It’s hard to say for certain whether a distro will work for your hardware, even the Nvidia-specific images can have bugs related to the Nvidia drivers or their interaction with compositors.

I’ve used NixOS for a year.

I also tried Fedora Sway Atomic for a week or so. It mostly worked well, but I eventually found that it’s really hard to use Nix for development on a graphics application, because linking with the system Vulkan drivers is near impossible. The loader used by Nix’s glibc will ignore FHS locations. That seems to rule out a lot of the benefits of using Nix.

So I gave up on using Nix + Fedora as a failed experiment and went back to NixOS.

My wish list for Nix, Wayland, and Sway is pretty long. I kinda wish I had the time to make a new distro.

Especially because devs actually have to go out of their way to exclude Linux these days. Proton makes it so damn easy to support Linux. If you don’t, it’s because you did not even try or you intentionally added some bloat to your software to make it incompatible.

If your goal is to “self-host” a password manager, you might as well use Keepass + SyncThing.

• free software
• master password protected
• has organization and auto-fill features
• can sync across multiple devices

Usually the downfall of rolling your own password manager is it’s easier to make mistakes and accidentally lock yourself out. Or if you don’t keep backups/replicas then you could easily lose your passwords.