I'll be the first to concede software issues aren't god-given (they're developer-given ... or imposed); being a developer this is something I basically preach to fellow developers. But a blanket statement of "it is just bad software" seems a bit over the top. I think snaps do indeed provide added value.
While I bemoan the fact that it's Canonical-driven, it _does_ add host- guest-separation. Both in the security sense and in regards to libraries within and without. It's just that this separation is working a little too well for a lot of real-world scenarios, it seems. To me the problem appears to be more along the lines of either adoption going faster than anticipated [1] and so development resources becoming a bottleneck, initial planning missing certain use cases (see above) or issues that arose from the combination of the two. So despite all criticism I uttered before (see above) I want to state that _I_ do not consider snapd bad software! [1] VLC would be a prime example of that. While obviously it could benefit from the added security (decoding file formats has long been a favorite target for exploits), the fact that I can't browse just anywhere means that packaging it as a snap may just be picking the wrong tool for the desired job. So works nice for Wekan, but for VLC not so much ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
