@miss_rodent Multiple distros means multiple platforms. Multiple platforms means multiple dev targets. Multiple dev targets means that developing for "Linux" is, at minimum, *many dozens of times more expensive* than developing for macOS, or Windows, or the web.
@glyph @miss_rodent But things like Flatpak exist.
@cthos @miss_rodent do they? experts seem to disagree
@glyph @miss_rodent I mean, I run several different distros across several different pieces of hardware, with different desktop environments and I can install Flatpaks on all of them, so yes?

@glyph @miss_rodent The list includes but is not limited to:
- Manjaro on a 2015 Macbook Air 11" with XFCE
- Bazzite on a Framework 13" with KDE
- ZorinOS on Starlabs Starlite (which IIRC is highly skinned GNOME)
- Vanilla Ubuntu on a weirdo 10" tablet PC thingie from Chuwi (Required some config to enable because Ubuntu really loves snaps and they shouldn't)

And all my applications just work.

@cthos @miss_rodent FWIW it's not *impossible* for this to work, but it is wildly beyond *cost-effective* for most ISVs
@glyph @cthos @miss_rodent Then the community should definitely organize to make Flatpaks work more reliably across distros. What are the biggest problems that make it necessary for app developers to put in distro-specific work even when targeting Flatpak? (I have no experience with this yet; my main desktop app project at this point is a remote desktop access tool, so that's a whole other can of worms.)
@matt @cthos @miss_rodent flatpak does not address the deficiencies or the expense of interacting with a zillion different compositors, or for that matter different audio systems or GPS daemons. the kinds of apps that need to interact with the platform need an API shaped in terms of d-bus endpoints, and the problem that flatpak addresses is one of .so files. flatpak also requires manual management of filesystem permissions, which means apps are just slightly dysfunctional
@matt @cthos @miss_rodent the main thing is that it is missing a macOS style powerbox file dialog (which, ironically, was originally invented in linux, via bifrost in OLPC)
@glyph @cthos @miss_rodent It looks like the File Chooser portal (https://flatpak.github.io/xdg-desktop-portal/docs/doc-org.freedesktop.portal.FileChooser.html) is supposed to implement a powerbox file dialog. I assume it somehow doesn't get this right.
File Chooser

Description: File chooser portal The FileChooser portal allows sandboxed applications to ask the user for access to files outside the sandbox. The portal backend will present the user with a file c...

XDG Desktop Portal
@matt @cthos @miss_rodent I have never seen an app do this in a way which appeared to work. my experience is limited though. glad to hear it at least exists though!

@glyph i had to look up what a powerbox was, but flatpak is built around the concept and wouldnt work without a functioning xdg file chooser that lives in the baseos outside the flatpak. Ive never had a problem with it, but ive only used flatpak on GNOME on Fedora, Silverblue and Bazzite, where its a first class citizen and well integrated. Flatpak can only be a universal app packaging runtime if it actually works on all the desktop systems without fuss and drama.

@matt @cthos @miss_rodent