

This contradicts their own wiki. Type 2 AppImages do use libfuse2, which is the problem
appimagekit is not actively developed anymore. Development moved to AppImage/appimagetool and type2-runtime
EDIT: Also go-appimage which was the first one to use the static runtime in 2022.
So no, they do not need libfuse2 anymore. Stop saying that nonsense, Download the AppImage of Cemu or PCSX2 or Ryujinx and remove libfuse2 and see for yourself…
Even in the github thread you linked it is said that namespaces are enabled by default in the kernel nowadays
Yeah and ubuntu recently fucked it up with namespaces restrictions.
Docker, where another kernel, package manager etc. gets loaded.
Docker doesn’t load another kernel, no idea if it can either, flatpak is pretty much another package manager as well. By your own definition it is another distro.
flatpak works by using bubblewrap which creates namespaces for the applications you use, essentially the root gets swapped for a fake root, this is how docker, podman, etc work.