Occurs to me that I likely have to make some kind of statement or whathaveyou about the whole "Solus adopting snaps" thing.

Long story short - having both flatpak and snaps, two independently diverging standards, has the following effect:

- Users have more choice
- Server software which falls outside of Solus package criteria can be catered for by Snaps (not flatpak. desktop only)
- Very importantly: We do not tie the leg of Solus to one specific implementation. Freedom is preserved both for users and the project itself.
- Delta in functionality with other distributions significantly reduced
- We initially adopted Flatpak as a solution to the "we-cant-distribute-some-apps" thing: That hasn't come about, Chrome still isn't flatpakable, and I've more faith in Canonical swinging a deal with Google for a snap than I have of flatpak gaining favour.
- Since that initial adoption, Snaps have been forced to evolve to meet the demands for inclusion in all repos, to become actually universal. Flatpak in that time evolved into a Yocto-based meta-distribution. We're not really dealing with the same factors as when we initially made the decision to choose one or the other.

Personally, I think everyone's lost their feckin marbles chasing universal apps as if its the #1 problem we have in Linux, as opposed to tangible attractive features to bring developers across and create awesome stuff for our platform too, but hey, whatever. :P In this instance we're able to empower the project and the users in one go.

The two most important things to me in that decision process is effectively "stuff we won't or can't distribute" - so props to +Martin Wimpress on the discussions we've had in that area. It's a handy way for people to get other bits on Solus. And obviously the other important factor is not being locked to a specific implementation.

Right, back to doing awesome stuff ...
Shared publiclyView activity