More specifically, issues for one distro (or maybe family of distros if applicable) and not other distros.
I’ll start: NixOS. I love how I can have my whole operating system configuration defined deterministically with configuration files, but what I believe is a serious flaw, is when you choose the “unstable” channel, the channel for receiving the latest packages rather than ones up to 6 months old: stable. Unstable package often build dependencies on device, and I’ve often faced build failures, why are new package versions given if they fail to build?!
Why can’t Nixpkgs backend ensure that new package versions build successfully before shipping them to end users?! It would take a lot of work to do so, but I can’t think of any other distros that have this problem: where installing a new package version that came out a few days or even a week ago, has a chance of failing after its made available in the distro’s official package manager.
There are a handful of workarounds for your NixOS configuration in this case, but it happens too often for me and I shouldn’t have to edit my config for to work around it.
I have been using bazzite for a while, and I’m quite happy with it, especially in the respect that it just does not break, ever.
But not can it be frustrating sometimes to install things that have no flatpak or appimage.
That being said, there are a lot of ways to get around this, homebrew and distrobox, etc. And its also not something the deva are sound wrong, it’s just part of the deal with immutable distros. Will frustrating at times though.
Yes it is frustrating but once you know that you can just enter a box and export the app, it’s not too annoying anymore.
I don’t feel a difference on opensuse aeon with vscode in a box.