> Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh.
i don't know when that line made it into the docs. i could be wrong but i actually thought that being evergreen was one of the selling points of snaps, and was advertised early on.
an edit: sorry upvoters - i went ahead and read the article now. i actually believe now that the article author has a point. to summarize: while it will display a notification to the user about two weeks ahead of time, announcing that an update is scheduled and that the user should close the app to avoid disruptions (the author has some valid complaints about this notification, i think), at the end of the period, the app will be killed - potentially causing unsaved data to be lost - and updated. i believe in many cases this behavior is undesirable. it probably should be discussed and a better alternative proposed.
i do take issue with the author's vehemence against (and manner of expressing such for) the notification, but i suspect i would be quite angry too if i were either an application maintainer fielding complaints about something that i didn't break, or a user who was angry to have lost some data.
oh i completely agree. i dont take issue with the content but the wording. i believe the poster said explicitly the developer was likely quite young. it bugged me. im old now, if anything i probably face the reverse kind of ageism. but i think that comment was ageist
edit: yeah, i looked it up, and i was right. i get the general feeling of a personal attack from the author's text in that paragraph, which irks me. i believe it is quite possible to argue against implementation or functionality without resorting to that sort of thing. its especially funny because the person clearly has no real idea of the situation and makes that clear. no need for that. i do agree with the content of the thoughts otherwise.
the repeated notifixation message from snapd that i need to close the app is really bad IMO...and e.g.closing firefox does not make the message go away(??), its very confusing
> Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh.
i don't know when that line made it into the docs. i could be wrong but i actually thought that being evergreen was one of the selling points of snaps, and was advertised early on.
an edit: sorry upvoters - i went ahead and read the article now. i actually believe now that the article author has a point. to summarize: while it will display a notification to the user about two weeks ahead of time, announcing that an update is scheduled and that the user should close the app to avoid disruptions (the author has some valid complaints about this notification, i think), at the end of the period, the app will be killed - potentially causing unsaved data to be lost - and updated. i believe in many cases this behavior is undesirable. it probably should be discussed and a better alternative proposed.
i do take issue with the author's vehemence against (and manner of expressing such for) the notification, but i suspect i would be quite angry too if i were either an application maintainer fielding complaints about something that i didn't break, or a user who was angry to have lost some data.