4 ms·

Nobody cares what changed, and nobody should have to care.

by krageon 4y ago

ben_w 4y ago
Unless it's a security vulnerability, I quite often find that I would have preferred for the update to never been made in the first place.
nneonneo 4y ago
I do care - I install tools because they're useful, and if they become more useful from new features, that's useful to know. I've definitely found some good gems to improve my workflow that I don't think I'd have discovered without the changelog. What I don't particularly care about is "performance optimizations and bug fixes". If that's all you have to say about your latest release, just don't bother telling me. I suspect that's where some of the fatigue from release notes comes from.
- KMnO4 4y ago
  I recently received a phone call from Dexcom, since they make a continuous glucose monitor that I wear. The call was to warn me not to upgrade to iOS 16 as their app would immediately crash and I wouldn’t be able to view my blood sugar. I was told a fix was being deployed and I would receive an email when it was safe to upgrade. Sure enough, a week later I received an email saying it was safe to upgrade to iOS 16, provided I updated the app in the App Store first. And as frustrated as I was that a company that large with a product so safety critical had waited literally months after the iOS betas before testing iOS16, I was more frustrated when I read the release notes for this incredibly important update: “Bug fixes and performance optimizations”
Ajedi32 4y ago
In most cases yes, but a change in ownership is definitely something I want to know about. I'd prefer a less intrusive way of notifying me of the change, but in this case the extension in question is one that works passively in the background, and doesn't have a UI that users regularly interact with. I can't really think of a better way to inform people, except maybe via the notification API?

4 ms·

Nobody cares what changed, and nobody should have to care.

by krageon 4y ago

Nobody cares what changed, and nobody should have to care.

ben_w 4y ago
Unless it's a security vulnerability, I quite often find that I would have preferred for the update to never been made in the first place.
nneonneo 4y ago
I do care - I install tools because they're useful, and if they become more useful from new features, that's useful to know. I've definitely found some good gems to improve my workflow that I don't think I'd have discovered without the changelog. What I don't particularly care about is "performance optimizations and bug fixes". If that's all you have to say about your latest release, just don't bother telling me. I suspect that's where some of the fatigue from release notes comes from.
- KMnO4 4y ago
  I recently received a phone call from Dexcom, since they make a continuous glucose monitor that I wear. The call was to warn me not to upgrade to iOS 16 as their app would immediately crash and I wouldn’t be able to view my blood sugar. I was told a fix was being deployed and I would receive an email when it was safe to upgrade. Sure enough, a week later I received an email saying it was safe to upgrade to iOS 16, provided I updated the app in the App Store first. And as frustrated as I was that a company that large with a product so safety critical had waited literally months after the iOS betas before testing iOS16, I was more frustrated when I read the release notes for this incredibly important update: “Bug fixes and performance optimizations”
Ajedi32 4y ago
In most cases yes, but a change in ownership is definitely something I want to know about. I'd prefer a less intrusive way of notifying me of the change, but in this case the extension in question is one that works passively in the background, and doesn't have a UI that users regularly interact with. I can't really think of a better way to inform people, except maybe via the notification API?