4 ms·
For many years my go-to plan has been to stay one point release behind apple's releases, especially the .0 releases -- but, times change. Last night I pushed th
by vessenes 5mo ago
For many years my go-to plan has been to stay one point release behind apple's releases, especially the .0 releases -- but, times change. Last night I pushed the button for 26.5, thinking about the Glasswing/Mythos reporting. Seems like staying on bleeding edge is going to be the name of the game.
I wonder if this will change general dynamics -- feels like LTS releases could become even more important, at the same time having reduced maintenance costs since you can have some agentic help on backporting.
- deleted 5mo ago[deleted]
- dragonsenseiguy 5mo agoSame! I almost never updated, now I feel like i need to update. Kinda feels like FOMO but for security updates
- samtheprogram 5mo agoSecurity updates still go out for older major releases back 2 versions. You didn’t need to jump to 26 if you weren’t on it.
- baq 5mo agoTell that to my IT department please
- mort96 5mo agoStaying one point release behind is weird isn’t it? I get staying a major release behind, Apple’s x.0 releases are often pretty rough so it might be worth staying on x-1 for a while. But point releases mostly just fix the stuff they broke in the major release.. Would you really upgrade from 18.5 or whatever to 26.0 when Apple releases 26.1?
- Marsymars 5mo agoPoint releases for macOS can be pretty large over the past several years - what often makes sense is waiting a few weeks to upgrade in case there's a .1 patch. e.g. macOS 15.0, 15.1, 15.3, 15.4, 15.6 and 15.7 all had .1 patches within a few weeks of release.