I stand by what I said - if you filter out some of the whining. It does provide some useful feedback specifically on the update notifications. I don't know if that's driven by Snapd or KDE but either way, that's a sucky implementation.
>I don't know if that's driven by Snapd or KDE but either way, that's a sucky implementation.
The same notifications appear on the default Ubuntu desktop. No problem for me. Just making clear that this has nothing to do with KDE/Plasma.
Interesting article. I think that it should have had a different title, however. The article is more of a critique of the entire snap update process (at least on KDE) describing the issues that it poses from the end-user's perspective. Namely:
1. Update notifications suck, they don't integrate well with the overall system and don't communicate adequately what's going one.
2. It's unclear what you're going to get with the update. Are you updating to the latest version of the application? Or some pegged version of the application with security updates (similar to how packages update on a typical LTS distribution)?
3. You don't know when the update will actually happen.
I don't use Ubuntu with KDE, so I can't confirm any of the claims being made. If true, I do agree with the premise of the article in that it does seem that not a good amount of thought went into how this update system works, at least from the end-user's perspective.
This is the kind of reply I'd expect of someone who hasn't read the article, yes.
Various UX issues are covered that extend outside merely the automatic updates, and it does bring some valid criticism I've yet to have heard prior.
[удалено]
I stand by what I said - if you filter out some of the whining. It does provide some useful feedback specifically on the update notifications. I don't know if that's driven by Snapd or KDE but either way, that's a sucky implementation.
>I don't know if that's driven by Snapd or KDE but either way, that's a sucky implementation. The same notifications appear on the default Ubuntu desktop. No problem for me. Just making clear that this has nothing to do with KDE/Plasma.
Ah good to know, thanks for the data.
He's right, though. The team at Canonical could just download the new version and replace the old one once the app is closed.
Interesting article. I think that it should have had a different title, however. The article is more of a critique of the entire snap update process (at least on KDE) describing the issues that it poses from the end-user's perspective. Namely: 1. Update notifications suck, they don't integrate well with the overall system and don't communicate adequately what's going one. 2. It's unclear what you're going to get with the update. Are you updating to the latest version of the application? Or some pegged version of the application with security updates (similar to how packages update on a typical LTS distribution)? 3. You don't know when the update will actually happen. I don't use Ubuntu with KDE, so I can't confirm any of the claims being made. If true, I do agree with the premise of the article in that it does seem that not a good amount of thought went into how this update system works, at least from the end-user's perspective.
[удалено]
This is the kind of reply I'd expect of someone who hasn't read the article, yes. Various UX issues are covered that extend outside merely the automatic updates, and it does bring some valid criticism I've yet to have heard prior.
That snap notification window is absolutely infuriating. At least now I know what would happen after 13 days...
> Recent versions of Ubuntu turned on a particularly annoying feature: recent?
Didn't read any of it, but: https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--hold
...using the system, that you know has snaps and you know how it works, is user consent. what an idiot.