3 ms·
How's that an argument? If they are stuck with Thunderbird 68 is because they don't want to update it. Same thing can happen with snap. If they don't work on i
by Darmody 6y ago
How's that an argument?
If they are stuck with Thunderbird 68 is because they don't want to update it. Same thing can happen with snap. If they don't work on it, you won't have the latest version.
- kd913 6y agoThe amount of development resources and effort needed to build publish and release the snap is a lot less than the apt. No need to interact with bzr, much easier to update in the snap store compared with repos. Snaps are built against one version, they easily integrate into CI pipelines (unlike launchpad/bzr) and you don't need to worry about things like outdated compiler versions (for releases on 18.04/16.04/14.04). I know because I helped with the CI builds of Firefox for snap.
- Darmody 6y agoBut again, bzr and launchpad are their own tools. If they are bad it's not an argument for snap. Other distros have their packages updated very quickly without snap.
- kd913 6y ago> But again, bzr and launchpad are their own tools. If they are bad it's not an argument for snap. This logic makes no sense whatsoever. If the previous tools are cumbersome and bad, and Canonical releases a new mechanism that is easier to develop/use/release. How the hell is that not an argument for the new mechanism? What is this logic? Nevermind that this new process is already integrated into several CI pipelines at Microsoft, VLC, Mozilla, Google, Amazon, JetBrains, KDE and Spotify.