5 ms·
You haven't really at all explained any justifiable reason for Canonical to open source it. You still haven't argued at all the resource aspects which are I thi
by kd913 6y ago
You haven't really at all explained any justifiable reason for Canonical to open source it. You still haven't argued at all the resource aspects which are I think the primary motivator here.
Canonical has done this experiment precisely in the past, and we see the results of nobody operating their own launchpad instance. Nobody contributing back. That experience probably trumps all of this goodwill and opinions from the community.
Canonical is more importantly getting users, publishers and numbers behind them. A discussion I remember reading was that every snap has 10x more installs than the corresponding flatpak. That and they have 1st party support from major publishers like Google, Microsoft, Amazon, Spotify, Mozilla, Jetbrains, KDE etc....
Those aspects are more important for usability for the average user.
- commoner 6y ago> You haven't really at all explained any justifiable reason for Canonical to open source it. I've explained why it would be in the users' interest for Canonical to open source the Snap store: it reduces vendor lock-in and allows the users to enjoy the benefits of open source software (the ability to use, study, share, and improve the software with no restrictions). Whether open sourcing the Snap server benefits Canonical is irrelevant to the users.
- kd913 6y agoNo you think it would be in the users' interest but it absolutely isn't. I'm willing to bet money you haven't looked at launchpad's source code at all. Nor have you or anyone else considered operating their own. That is how most of the Ubuntu based distros right now are already getting their software. If Canonical goes down, a huge part of the usable linux market goes down with it. Possibly Linux Mint too, unless im mistaken. >vendor lock-in You are not vendor locked in. You can install flatpak, install via apt, appimages etc... Canonical doesn't ban the removal of snapd from ubuntu distros. In fact, from a Linux dev I would argue that half the fragmentation for pointless nonsense like packaging and distributions has harmed the community far more. Namely because it's increased the cost of development for these things to a degree that companies won't even bother developing/publishing software on Linux. That has been the primary problem for Linux so far. Canonical is actually getting first party support from major publishers and people still lampoon them. This includes publishers in the past who never would have considered publishing for Linux before.
- commoner 6y ago> No you think it would be in the users' interest but it absolutely isn't. If you don't understand the value of free and open source software, you're not obligated to use it. The maintainers of Linux Mint and other Linux distributions do understand, and that is one of the reasons they have rejected Snap. > I'm willing to bet money you haven't looked at launchpad's source code at all. Nor have you or anyone else considered operating their own. Your assumption is wrong and you've lost the bet. Additionally, Flatpak is available and Flatpak servers are already being hosted independently: https://www.google.com/search?q=%22our%20flatpak%20repo%22 https://www.google.com/search?q=%22our%20flatpak%20repo%22 > You are not vendor locked in. You can install flatpak, install via apt, appimages etc... Canonical doesn't ban the removal of snapd from ubuntu distros. Canonical has already transformed apt installs of Chromium into Snap installs, which motivated Linux Mint to reject Snap. Vendor lock-in is not black and white. For example, Android users can also install F-Droid or a variety of third-party app stores, but considering Google Play's default status on Android, most users are effectively locked in. The same applies to Canonical's handling of Chromium, and the Linux community is opposing this to discourage Canonical from continuing this dark pattern. > half the fragmentation for pointless nonsense like packaging and distributions has harmed the community far more Snap increases the fragmentation, and is more hostile to the FOSS community than all of the other options because its server is closed source.
- kd913 6y ago>If you don't understand the value of open source software, you're not obligated to use it. The maintainers of Linux Mint and other Linux distributions do understand, and that is one of the reasons they have rejected Snap. I understand the value of open source software. I work for the industry building open source drivers and contributed back. But providing/producing and maintaining software isn't free and that is precisely the main motivator that you don't seem to pay attention to. It's all good using a 100% FOSS stack, but that is irrelevant for the average user who wants to use things like Office, Steam and Spotify. The lack of usable software holds back Linux Desktop. So does your almost Stallman esque attitude to this. >Your assumption is wrong and you've lost the bet. Additionally, Flatpak is available and Flatpak servers are already being hosted independently: So you are hosting your own launchpad instance? Please do show me, that and all the wonderful contributions you have made to Canonical to have justified the massive resources they undertook by open sourcing it. >Additionally, Flatpak is available and Flatpak servers are already being hosted independently: That is a negative which I have argued multiple times. Multiple locations to have to find software which makes finding useful software harder. The user has to trust random third parties which breaks security. Yea, Canonical had all those experiences with PPAs and how much of a nightmare that has been. >Canonical has already transformed apt installs of Chromium into Snap installs, which motivated Linux Mint to reject Snap. Vendor lock-in is not black and white. For example, Android users can also install F-Droid or a variety of third-party app stores, but considering Google Play's default status on Android, most users are effectively locked in. The same applies to Canonical's handling of Chromium, and the Linux community is opposing this to discourage Canonical from continuing this dark pattern. Funny you are saying this and advocating OpenSource and all this nonsense. Do you know why Canonical moved the chromium binary to snap? It's because maintenance costs were ridiculous. They had to backport their compiler and support versions from 14.04 to 19.10 at the time. They couldn't backport the compiler, and because chromium is a browser, users must be on the latest version for security reasons. It also deeply integrates with the OS via the Linux specific sandboxes which do not work the same from 14.04 to 19.10. This they were maintaining for FREE. They didn't even have to do this because the officially supported browser is Firefox. They didn't want to burden the cost for this nonsense and rightfully moved it to snap. Where is Mint here providing the maintenance costs/burden for providing chromium as a deb here. Canonical explained it clearly here. https://ubuntu.com/blog/chromium-in-ubuntu-deb-to-snap-transition https://ubuntu.com/blog/chromium-in-ubuntu-deb-to-snap-trans... >For example, Android users can also install F-Droid or a variety of third-party app stores, but considering Google Play's default status on Android, most users are effectively locked in. You are delusional if you think the situation is anywhere near the closed wall aspects of Android. Canonical doesn't operate it's own safety net or attestation that bans F-Droid or any other distribution. They don't have any controls or inhibitions in place for how users install/distrubte software unlike Android. >Snap increases the fragmentation, and is more hostile to the FOSS community than all of the other options because its server is closed source. You seem more hostile to the goals of the FOSS community than they are in my eyes. The person who is preventing Steam Games, WINE, Adobe software etc.. from coming to Linux is people like you. They can reject snap all they want.