<\/p>\n\n\n\n
It sounds cool: having a single package format that is “easy to install, secure, cross-platform and dependency-free<\/a>“. Because it is hard to maintain all these different versions for all those distributions and platforms. Unfortunately, Snap is not a solution. It is yet another problem for the Linux desktop.<\/p>\n\n\n\n\n\n\n\n Such a good idea<\/a>: a new software installation package type that has all libraries and other dependencies included. Let the central resource facility<\/a> handle updates. Isn’t that how the Play Store, and Apple Store handle their business, too?<\/p>\n\n\n\n Snap was built around a security model, a snapped application runs inside a container that will only see what it is supposed to see. That causes trouble. For example: if you try to view a It gets worse. Opening an e-mail with a And don’t get me started on stupid bugs like the snapvertized Thunderbird installer copying your entire mail<\/a> folder, even if it is gigabytes of cached mail messages, from Then there are extremely silly bugs like LibreOffice cannot open files on a SMB share<\/a>. Yes, you read that correctly: you cannot read files from the network<\/strong> with a snapped Libreoffice.<\/p>\n\n\n\n Now you may say that this is all temporary, oh bugs need to be fixed and wrinkles straightened out, but hey, even a simple Clicking on a link in a PDF document that didn’t work<\/a> took five years<\/strong> to fix – and not even for all browsers you can think of<\/a>. You really do think that any end user will want to wait for five years to get functionality back? So how is this easy to install<\/em> if it gets you software that simply doesn’t function after you installed it?<\/p>\n\n\n\n Adding layers to complex software makes the software more<\/em> complex. More complex to maintain, more complex to debug. Complexity is the enemy of security. Because if you can’t debug, you cannot fix.<\/p>\n\n\n\n Take the Linux printing system. Openprinting Cups<\/a> is a wonderful and complex piece of software with parts of it dating back to the earliest Unix printers – probably more than 25 years old. It supports a ton of printers, printer protocols, network protocols, autodetection, printer language conversion. But after all these years, even the printer maintainers find the build process a bit too complex<\/a> to be able to debug. Now Canonical has found out that life is going to be more secure by adding<\/strong> a layer? These days, I don’t even know where to look if I want to see where a printer was defined: is it Snap cupsd or is it cupsd.<\/p>\n\n\n\n Yes, I did read that “outdated devices” are a huge problem and that that was one of the reasons for Snap to come to life. The main reason<\/em> I’m not upgrading is, in most cases, that I know or suspect that my New And Improved package just doesn’t work<\/em>. So while Snap may make upgrading<\/em> easier, it gives me plenty of reasons to not install it in the first place.<\/p>\n\n\n\n Then there is the cross platform promise. This seems to be limited<\/a> to Snapped Linux distributions and the Microsoft Windows Subsystem for Linux (WSL). My personal opinion is that Windows is a piece of marketeer-driven junk – with ads on the desktop and an absolute vow to not make it easy for anyone to escape the tightly controlled Microsoft ecosystem. So if Snap actually does make software installation easier on WSL, it probably helps Windows users stay on Windows longer<\/em>.<\/p>\n\n\n\n I just hope Canonical makes loads of money with it but I don’t think the cross platform helps me<\/em> (or any Ubuntu Linux user) in any way here. Or is there any software Out There that didn’t have an Ubuntu install file – but is on Snap?<\/p>\n\n\n\n So Snap is broken. It gives me packages with bugs, cross platform compatibility for a platform I’m not using, obscurity during debugging. And most unfortunate of this all is that bugs that would<\/em> need action for the Linux desktop to become more usable, will just have more competition<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" It sounds cool: having a single package format that is “easy to install, secure, cross-platform and dependency-free”. Because it is hard to maintain all these different versions for all those distributions and platforms. Unfortunately, Snap is not a solution. It is yet another problem for the Linux desktop.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,22],"tags":[9,32,202,7],"class_list":["post-1218","post","type-post","status-publish","format-standard","hentry","category-opinie","category-vrije-software","tag-linux","tag-open-source","tag-snap","tag-ubuntu"],"_links":{"self":[{"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/posts\/1218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1218"}],"version-history":[{"count":13,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/posts\/1218\/revisions"}],"predecessor-version":[{"id":1237,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=\/wp\/v2\/posts\/1218\/revisions\/1237"}],"wp:attachment":[{"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/valentijn.sessink.nl\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}.html<\/code> file that is sitting inside a .zip<\/code>, this won’t work<\/a>. Because the file.html<\/code> inside the zip-file is temporarily extracted to .cache\/.$randomname\/file.html<\/code> and Firefox<\/a> cannot (i.e. is not allowed to) look there. Same for PDF files and Evince (the PDF viewer). The “normal” Evince (installed from a .deb <\/code>file) will see your unpacked PDF just fine, but Evince Snap complains: Unable to open document: Permission denied<\/em>.<\/p>\n\n\n\n.docx<\/code> or .odt<\/code> attachment from Thunderbird<\/a> – apparently – opens Libreoffice<\/a> from within the Thunderbird Snap confinement. Libreoffice has the nice feature of opening all documents in one instance. So any additional<\/em> document you’re trying to open will fail – because they are outside of the Thunderbird container. You must close the Thunderbird invoked Libreoffice<\/strong> before you can edit other files. Or something. I didn’t research this further, sometimes enough is enough.<\/p>\n\n\n\n.thunderbird\/<\/code> to snap\/thunderbird\/common\/<\/code>. (Did Canonical sign a sponsor deal with the storage industry?) This – obviously – will not work if the profile is too large – in which case the migration simply fails<\/a>. The tracking bug for Mozilla Snap issues<\/a> has 86 bugs open and this includes severe bugs like the profiles.ini file not being migrated correctly<\/a> – this bug is open since september 2021. The fact that you will have to recreate the link to your signature if the signature file is outside of the copied profile is such a minor detail that I did not even bother to file a bug (it would be number 87). See this<\/a>, that’s more important than an e-mail footer.<\/p>\n\n\n\nSecurity<\/h2>\n\n\n\n
Cross platform<\/h2>\n\n\n\n
Broken<\/h2>\n\n\n\n