4 ms·
And it's a pretty good one since the experience with having a large catalog of useful software in Flatpaks has been awesome and largely seamless. I just wish Ca
by Spivak 7y ago
And it's a pretty good one since the experience with having a large catalog of useful software in Flatpaks has been awesome and largely seamless. I just wish Canonical wasn't off doing their own thing or had started out in the open from the start so it would have a chance of being a useful standard instead of the weird Canonical store.
- vetinari 7y agoThe number one reason why I don't like snap is: it puts Canonical in control. Only Canonical can run a store. Once you install something, Canonical decides, when packages on your computers will upgrade. Wrt control, it goes way beyond Apple store/Google Play/Microsoft Store. No thanks. Flatpak can preserve the benefits of decentralized repositories and upgrade under user control, with all the ease of packaging and sandboxing of the new toys.
- sq_ 7y agoI can never figure out Canonical's logic with going off to do their own thing. They don't do it with everything, so clearly it's not a complete rejection of things not made in-house. It seems like they also often end up going back to the community solutions/standards eventually, so what benefit do they see in doing this over and over again?
- mulmen 7y agoDoes it force the community solution to improve? If the options are community or Canonical does that competition have benefits to both? Not sure Canonical are thinking that explicitly but maybe it’s just hedging their bets if the community solution doesn’t work out.
- fapjacks 7y agoBut this is a false dichotomy, because Flatpak is a project controlled by Red Hat. Unless by "community" project you mean AppImages.
- mulmen 7y agoI'm speaking in general, this would also include the Gnome churn a few years ago. Canonical seems to build their own thing then abandon it in favor of what the community was doing before or during the development of the Canonical thing. I'm just spitballing why that may happen.
- the_why_of_y 7y agoFlatPak is a project initially hosted on freedesktop.org infrastructure with distributed copyright ownership under a copyleft license. It was initially founded by Red Hat employees but has attracted substantial support and contributions by companies such as Endless and Collabora, not to mention volunteer contributors. The sandboxing part was spun off to the bubblewrap project, which has been adopted by the community for other purposes, such as Gnome's Epiphany browser. https://github.com/containers/bubblewrap https://github.com/containers/bubblewrap https://blogs.gnome.org/mcatanzaro/2020/03/11/epiphany-3-36-and-webkitgtk-2-28/ https://blogs.gnome.org/mcatanzaro/2020/03/11/epiphany-3-36-... SnapCraft on the other hand is a project that requires copyright assignment to Canonical Ltd for contributions, which presumably has the intended effects of keeping non-Canonical contributions close to zero. https://github.com/snapcore/snapd/blob/master/CONTRIBUTING.md https://github.com/snapcore/snapd/blob/master/CONTRIBUTING.m...
- fapjacks 7y agoConsidering that Flatpak was essentially a hostile fork of the AppImage project motivated by Red Hat's insatiable hunger for control, I find it ironic when Flatpak supporters complain about Canonical "doing their own thing".
- the_why_of_y 7y agoFlatPak has nothing to do with AppImage, is in no way shape or from a fork of it. https://blogs.gnome.org/alexl/2018/06/20/flatpak-a-history/ https://blogs.gnome.org/alexl/2018/06/20/flatpak-a-history/ AppImage only solves the easy part of the generic-linux-app problem, namely running the packaged appimage; it does nothing to solve the hard parts: how do you build the application so that it will actually run on generic Linux distributions, and sandboxing.
- thecureforzits 7y agoGot a source for any of those claims?