@Ulf I actually wouldn't recommend Debian for desktops at all, and I definitely wouldn't recommend it for beginners. Debian suffers terribly from stale packages, which people running servers seem to like, so it's more an LTS type of OS for server admins. Debian, even unstable, also tends to mix versions of components of desktop environments. I ran a Debian stable system for a time, and needed an upgrade to the latest GNOME for #a11y purposes. Looking at the packages, I saw two different versions of the components of the GNOME desktop, even in the stable branch. Upgrading to unstable gave me three versions of the components. Even experimental didn't help.
I'm actually more likely to recommend Fedora to new users, as it keeps everything grouped together by its major versions, has an easy to use installer, has flatpak enabled and working by default (flathub support coming to 38), has snap and podman available, has a predictable release lifecycle, and only withholds updates if they would break something. These days I use the MATE desktop, a11y and I just like the interface, and the only version mix I see is point releases of a couple of things where some packages see point releases upstream and others do not. Major versions are always in sync. Following GNOME developments, I see the same thing here. I have been running Fedora since 35, have upgraded quite smoothly all the way to 37, and haven't had any major problems. Maybe it lacks the polish of Elementary or Mint with their downstream modifications that make things look better and maybe more beginner-friendly, but Fedora is definitely good for both new users and oldheads like me, and it seems to work more closely with upstream developers, even though it is in actuality more of a corporate distro like Ubuntu. I especially like how it withholds nothing from us, giving us its own package management system, Flatpak, Snap and Podman. The only thing I find missing are the appImage tools that build appImages and the appImage launcher that automatically registers appImages on the system, but I'm hoping these things can be added at a later date.
Regarding appImage not having a central repository, there is AppImageHub, but the best part is its decentralized nature, where I can have a project website, offer my appImage for download right on the website, and I can even supply a checksum that can be verified so that anyone who wants to ensure they have my release and not some kind of compromised malware can verify it. As Flathub is essentially becoming its own corporate walled garden of a sort, complete with financial subscriptions, the beauty of appImage is in its decentralization, especially since no appImage ever has to be installed. They just work(tm).
I have no experience with Podman, so I can't make an argument for or against it, except that I did try playing with Docker containers and found them quite clunky for running server applications. For example, why should I run 5 Docker containers to get 5 websites working? That uses more RAM and more disk space than just setting up virtual hosts for the 5 sites. Then again, reverse proxies work with or without containers, but the Docker images are just so much larger and are harder to get running. AppImages are in fact larger than the system packages, but it seems running so many Docker containers is even larger. Still, if Podman makes this easier and less clunky, then I would certainly be willing to give it a shot. But I can more easily reverse proxy to an appImage than I can get a Docker container working at this point. Perhaps it's just me, as I like to take the easy route wherever possible.
