3 ms·
I think the author of the article brings up a good point regarding this, though. If you're a non-technical user, you're not going to read it at all. You might u
by pc86 6y ago
I think the author of the article brings up a good point regarding this, though. If you're a non-technical user, you're not going to read it at all. You might update, you might not, but you're not going to look through the list of changes.
If you're a technical user, you know it's unlikely that update == "more crashes and slower load times" so saying the opposite isn't helpful, and a list of things might be helpful.
So as a user of an app you probably fall into one of 3(ish) categories:
1. You read the changelog and something is relevant to you.
2. You read the changelog and nothing is relevant to you.
3. You don't know what the changelog is.
Listing the bugs that are fixed helps some of these groups. "Bugfixes and performance improvements" is a given, and helps no one.
- jfengel 6y agoSome non-technical users do read change logs, looking for new features. Even if they take every update, the notification of an update pings the hope that there may be something useful or fun. "Bug fixes and performance improvements" means "you need this update but there's nothing you really care about". So there are least two kinds of updates, those with user-facing features and those without. Currently both come in the same stream. We could come up with a better way of differentiating the two, including not notifying users at all when the boilerplate "fixes and performance improvements" comes on. Just update the app and what the user doesn't know (hopefully) won't hurt 'em.
- grayclhn 6y agoEven when I'm in group 2 and don't want to read every update, I'm reassured by the fact that users in group 1 can find relevant information. I also sometimes move from group 2 to group 1 when I need to track down what version introduced something that's just now causing me problems. :)
- toast0 6y ago> If you're a technical user, you know it's unlikely that update == "more crashes and slower load times" so saying the opposite isn't helpful, and a list of things might be helpful. It's precisely because an update might bring more crashes that I'd like to see what changed.
- a1369209993 6y ago> If you're a technical user, you know it's unlikely that update == "more crashes and slower load times" so saying the opposite isn't helpful, and a list of things might be helpful. Umm, no; if you're a technical user, you know it is likely that update == "more crashes, slower load times and useful features breaking or disappearing entirely", regardless of what the changelog says, because you've observed exactly that happening with eg your webbrowser or image editor. > "Bugfixes and performance improvements" [(]is a given[)], and [(]helps no one[)]. Well, you're half right.
- brewdad 6y agoI tend to fall in either 1 or 2 depending on whether I've been bitten by a specific bug and need to know if it has been fixed. The worst changelogs are the ones that say "Performance improvements and bugfixes" only to find out the entire user interface has changed after updating.