3 ms·
> “As a developer of macOS security tools, it’s incredibly frustrating to time and time again have to deal with (understandably) upset users (understandably) bl
by move-on-by 2y ago
> “As a developer of macOS security tools, it’s incredibly frustrating to time and time again have to deal with (understandably) upset users (understandably) blaming your tools for breaking their Macs, when in reality it was Apple’s fault all along,”
I would like to understand this better. Were there not any beta releases that these companies could have tested with in advance? Or were changes made between the beta and the release that broke things? Or something else?
- Spivak 2y agoThis is the part I'm missing too. Major versions are the time to ship braking changes, did none of these companies bother to test their software that mucks deep in the plumbing of the OS?
- 1over137 2y agoIt is very typical to file bugs against even the first beta and not see them fixed before GM, or even ever.
- RockRobotRock 2y agoIs there even an equivalent to WSUS on macOS that lets admins block an update until it's tested?
- salmo 2y agoYeah. There’s Jamf and similar tools. Companies often block major updates until their 100 agents all officially support it. Oh, and do cool things like not letting you change your background or whatever random settings some admin decides are good.
- ripa 2y agoYep, a lot of these policies seem to come from some random person scrolling through a list of supported options and arbitrarily making up values that are enforced on people. One of our policies enforce that screen savers must start after 20 minutes, and it’s not possible to reduce it (I have my personal on 3 minutes). Or the fact that it will constantly reset the UI notification volume to 100% and speaker output, even though have headphones almost always. Infuriating.
- colechristensen 2y agoYes, it's called MDM (Mobile Device Management) and lets admins set all kinds of policy on apple devices. There are several vendors out there that implement it.
- wpm 2y agoThere is a configuration profile payload that can stop updates like major version changes for up to 90 days. You cannot stop them indefinitely from appearing in Software Update.
- eviks 2y agoThey did, reported it, nothing changed. It's an OS bug, you can't make it look good by invoking some generic "time to break" principle
- sephamorr 2y agoPer Patrick Wardle, this was well reported to Apple during beta. https://x.com/patrickwardle/status/1836862900654461270 https://x.com/patrickwardle/status/1836862900654461270
- move-on-by 2y agoThank you, this makes the frustration in the above quote more understandable. For anyone wanting to avoid the x click: > Worth stressing this was reported to Apple before the GA was released (by multiple people, to multiple teams/orgs within Apple) so Apple 100% knew about this, and shipped macOS 15 anyways
- MichaelZuo 2y agoApple, or at least their teams responsible for answering feedback, rarely ever give substantial responses nowadays, regardless of how well documented the submission was. So it compounds the frustration. And this isn’t even the most egregious case, sometimes the bugs are so obvious that they generate multiple hard faults, per hour, logged in Console, on a fresh installation with only the default apps running.
- pcdoodle 2y ago[flagged]
- bzzzt 2y agoIMO those Mac anti-virus tools are basically malware exploiting all kinds of loopholes and hacks to get their hands on everything going on in the system. It's a good thing Apple fixes those loopholes and it's not Apple's responsibility to make sure every hack used by these tools keeps working.
- jhbadger 2y agoI'm not a big fan of these tools myself (although like many people my employer insists on them). But still, isn't it the responsibility of the tool maker to make their software work with new OS versions and not Apple's?