This is just a straight up lie. Flatpaks do share libraries, both as runtimes (as seen even in the screenshot here) and through deduplication between different runtimes and runtime versions. There’s usually very little bloat, if any, especially if you use Flatpaks a lot, which you probably should, given the huge number of advantages especially with proprietary apps.

There’s also deduplication across the different files. So you could even end up with less overall size over time if you use Flatpaks for everything.

Take your own advice

Why would you want the app devs to make that? The whole problem with distro-specific packages is having to package for multiple formats and it’s a painstaking process that really isn’t worth any amount of time investment at all. If you’re an app developer, you’d much rather just make a universal package and hope that some distro package maintainer packages your app for their distro. That’s just basic common sense…

Worst case scenario is that you run just those commands in sh. I don’t see a problem really. I also like fish’s syntax, so it’s easy to trade for POSIX compatibility. If you really really must, you could also use an LLM to convert your bash script to fish.

Ever since switching to fish, I’ve been using the terminal more and more. It’s the most intuitive interface I can think of. Now to fix my neovim configuration…