It is quite annoying that functionality just changes on products I buy. I hate applying updates because rarely are they an improvement. Sometimes it's just reduced functionality
And it's not like "hey in 6 months we're going to be implementing this change, so get ready in case it affects your workflow" it's sprung on you with no warning and no options, and often isn't even clearly communicated after the fact.
- poor testing between front and backend so that ppl don't know what versions of apps can work on that versions of apis, so forcing updates, "just to be safe"
- security slop - forcing the update of apps because they have an insecure library, like curl, so inane policy forces them to update...
On Debian, you can choose to only have automatic security updates. So nontechnical people can just use it and never have any system-relates support requests.
It is quite annoying that functionality just changes on products I buy. I hate applying updates because rarely are they an improvement. Sometimes it's just reduced functionality
https://www.sammyfans.com/2025/04/16/samsung-explains-why-bl...
Or sometimes it's destructive. Postman update removes all your stuff if you refuse to create account
https://news.ycombinator.com/item?id=37792690
And it's not like "hey in 6 months we're going to be implementing this change, so get ready in case it affects your workflow" it's sprung on you with no warning and no options, and often isn't even clearly communicated after the fact.
Two main reasons i see:
- poor testing between front and backend so that ppl don't know what versions of apps can work on that versions of apis, so forcing updates, "just to be safe"
- security slop - forcing the update of apps because they have an insecure library, like curl, so inane policy forces them to update...
On Debian, you can choose to only have automatic security updates. So nontechnical people can just use it and never have any system-relates support requests.