5 ms·
> I lean more toward Flatpak as it is more performant What is "performant" supposed to mean here? Is Flatpak faster than Snap? more compact? simpler? more rel
by musicale 7y ago
> I lean more toward Flatpak as it is more performant
What is "performant" supposed to mean here?
Is Flatpak faster than Snap? more compact? simpler? more reliable/secure? easier to use? more efficient in terms of cpu/memory/communication/power/etc.? all of the above?
- djsumdog 7y agoI always had problems with both of them. I use Docker a lot and Flatpak/Snap are intended to be a type of Docker for desktop apps. I know with Flatpak it has some shims to integrate with your system UI libraries so themes try to match up, but there are issues with that too (and flatpak apps just not starting up half the time). I really hate Snap/Flatpak conceptually. Use the package manager. That's what it's there for. FPM is a way to make package building easier. Snap/Flat tools feel like they're about the same as Electron cancer; and I bet we'll see more closed source commercial stuff pushed to the Linux world via them as well.
- RMPR 7y agoFlatpak is marketed as a better Snap (it surely has some advantages: no vendor lockdown), but at the end of the day, the system integration is not that good, I tried to use the Flatpak of Wireshark back in the day when I tried Fedora Silverblue, I ended up regretting that experiment.
- Koshkin 7y ago> a type of Docker for desktop apps By the way, what is it with Docker that makes it hard or impossible for it to be used for this exact purpose?
- mixmastamyk 7y agoDocker is poorly designed as well.
- appleflaxen 7y agocan you elaborate? I can google for "docker sucks" blogposts, but I trust the HN opinion to be a bit more thoughtful. Any specific pain points you can identify?
- sylvain_kerkour 7y agoI think what the author wanted to say is that the tradeoffs made by Docker's authors are different than those he would have made.
- mixmastamyk 7y agoThe most commonly mentioned flaw was/is the root daemon. That can be worked around with other tools. The command line and docker files are a bit clumsy as well. Many images have security flaws. It didn’t clean up after itself for a looong time, etc. It doesn’t “suck,” and many of the ideas are compelling. But, the design and implementations could be better. I was interested in rkt until it was acqui-abandoned.
- Kaze404 7y agoIt's not that hard. I remember using it to run Slack at one point, and while it wasn't easy it's definitely possible if you need it bad enough.
- fulafel 7y agoDesktop apps are not designed to operate in isolated fs namespace/network/etc from the host. So the user experience won't be seamless unless there are standards that enable desktop apps to be aware of how they are dockerized. Which there aren't afaik
- curt15 7y ago>Is Flatpak faster than Snap? Snap suffers from the overhead of having to decompress a squashfs on program launch: https://forum.snapcraft.io/t/squashfs-is-a-terrible-storage-format/9466 https://forum.snapcraft.io/t/squashfs-is-a-terrible-storage-...
- zaro 7y agoLaunching app from snap is noticeably slower than from native package. My experimetsn on the same laptop showed that.. Launching Skype installed from deb is almost instant. From snap it takes around 10sec to get anything to show. This is on quite fast nvme disk.
- PlutoIsAPlanet 7y ago> Is Flatpak faster than Snap? Yes, Flatpak is just bind mounts and namespaces. It doesn't have the overhead of the squashfs images.