You must log in or register to comment.
My organization has always held back new MacOS releases until the IT team completes internal testing and validation. This is pretty typical and enterprises should be used to this.
Bugs aside, new releases may have behavioral changes and that’s true of any OS.
Smart IT departments do this with Windows upgrades too. Even though Microsoft is usually very good about backwards compatibility, it’s always smart to test these things before you upgrade 500 computers.
A few year back it wasn’t rare to find company who were running two years behind windows update.
The fact that 90% of corporate stuff now runs in the browser has alleviated most of the upgrade issue.
Smarter it departments use the developer/beta builds to test this so day one updates shouldn’t be a problem.
People paid good money for this software, they shouldn’t have to get used to this.
The software is free. They bought the device.
Paid good money for a seatbelt, doesn’t mean I’m gonna drive into a tree
Does your seatbelt update mid operation so its function changes?
The problem is the vendors for not figuring this stuff out when they had dev access available for a very long time.
We were held back more than a year when one company took that long to make their software compatible. They even blamed it on Apple when it was obvious that they only cared about Windows customers. We moved on to a different product soon after.
The update prevents CrowdStrike from working. That’s a good thing!
CrowdStrike blew it. 3rd party vendors should never have the power to freeze or crash people’s computers through incompetent, untested updates!
Yeah, frick the userland.
