The title is a quote from Mastodon. I’ve always seen dislike towards snap so I was taken back when I saw this stance. The person who wrote this was referring to Tuxedo Laptops.
I posted my question here before this particular response from the OP. I asked the question on Lemmy out of interest and wanting to get a wider perspective. I also engaged with the OP on the thread so that I can get their perspective on their stance.
There already is Flatpak. Many proprietary apps are shipped as Snaps, which helps with Flatpak packaging as the binaries can just be packed into a different container.
Snap developers kinda help with making the whole portals, isolated apps stuff work.
The Venn diagram of supported apps isn't also a perfect circle. You can't run VPNs as Flatpaks, and Flathub disallows CLI apps from being submitted (because the UX of using a sandboxed CLI app sucks). Snap doesn't have these issues.
Others like valve have just ignored the issue for years, but the flatpak devs decided to argue that it doesn't apply to them, to the point that one even mentioned modifying the spec so that they are exempt...
Yeah that's solidly it. I use strictly confined CLI snaps all the time. (In fact, I maintain the snaps for a couple of CLI apps.) They work fine as long as the snap has the right plugs.
But I don't want to have to run flatpak run dev.htop.htop to get to htop.
Helix opens it's own GUI when you run it. It's not a CLI app in the same sense as git. I'm curious on the others you mention, since as a packager, I've seen firsthand CLI apps being declined (or allowed, but only with a hidden status on flathub.org)