150
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Nov 2023
150 points (97.5% liked)
Technology
34571 readers
478 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 5 years ago
MODERATORS
I can't with this article... there's a very legitimate argument to be made here, but instead they are whining that stuff stopped working after an iOS update. If you're running something life-critical you do not install every single update the moment it comes out.
I couldn't disagree more with you. If you are running something REAL life critical the moment there is a patch you install it and deploy as fast as possible. And if it contains any severe patch it is even the vendor who recalls all the equipment with service bulletin and advisory letters.
With life critical you don't wait the bug to appear because It maybe too late to avoid deadly consequences.
Then we disagree. Think about it, you're patching the OS so what you now have is an untested configuration, and you've replaced a working system to get there, on the theory that you might be preventing an unknown bug in the future.
In one instance the vendor even explicitly recommends disabling OS updates until they have tested them.