Thanks for this… as it happens, I don’t use Safari, but I do use Chrome and Brave, and, generally speaking, I use a VPN, depending on where I’m going online.
1 Like
5 posts were split to a new topic: What ad blocker do you prefer?
FWIIW Firefox is still supported on my “retired” iMac running Mojave (used as a media server). Every few weeks Firefox alerts me to an update. So I don’t expect Monterey will be a problem.
Agreed. Don’t forget to keep an eye on the Firefox release schedule, though. Mozilla says that they will make a decision on support for Firefox 115 ESR on Mojave sometime next month:
We decided to extend support for ESR 115 only on Windows 7-8.1 and macOS 10.12-10.14 up to September 2025 . We will re-evaluate this decision in September 2025 and announce any updates on ESR 115’s end-of-life then.
1 Like
I’m definitely keeping an eye on that. If Firefox stops supporting macOS 10.12 (Sierra), then I’ll have to pick from two choices for my 2011 MacBook Air:
- Buy a new Mac laptop. Which will probably be an base model 13" M4 Air ($1000 from Apple or currently $800 from Costco)
- See if I can use Firefox Dynasty. It’s currently at version 142.0 (the latest official Firefox release is 142.0.1), so it’s a good option if it works.
1 Like
When I applied the update to my M2 Macbook Air it wouldn’t reboot. The message was that my firmware was corrupted. Had to use another mac (what if I didn’t have one!) and about 1.5 hours of time to “revive my firmware” (which worked). If not, the only other alternative was to “restore to factory settings” and load my latest time machine backup (which was about 3 weeks old). Did anyone else have this problem? I just turned off “Automatic Update”.
I did not. Neither on an M4 nor on an M1 MBP.
Apple stores will help. And I assume so will authorized dealers. Obviously, that’s not convenient if you’re far away. Perhaps a neighbor or friend close by could help.
An excellent reminder to all of us to always keep an up-to-date backup. If you modify files, apps, and/or settings on a daily basis, you probably also want to make sure you have an at least daily backup.
IMHO that’s a good idea. Most will want to keep Install Security Responses and system files on though.
Settings > General > Software Update > Automatic Updates > click on the circled i
1 Like
My 2019 MacBook Pro (Intel) applied the update automatically with no problem. But I am nervous for my Mac Mini M1, which is my main file server. (And it is backed up by Time Machine AND Carbon Copy Cloner nightly.)
I’ve always heard “wait a week to see if there are any problems”. Now I’m a believer :)
Anecdotal of course, but I’ve installed it on my M2 MacBook Air (my main productivity machine) and my M1 Pro Mac mini (a media server, plus a few other server type things - my main Syncthing repository, my main backup source for online server accounts, my spamsieve monitoring device, plus it also monitors my other devices to look for loss of connectivity). Both installed without an issue at all.
Fair enough… But once you’ve figured out what and how to test, doing the tests can be ‘parallelized’ across many workers.
Depends on the nature of the testing.
It requires particular skills to design proper tests and develop test-automation scripts and tools. These skills have a bit of overlap with software development skills, but they are distinct. Developers do not generally make for good test engineers.
Once the tests and scripts have been developed…
Junior engineers can launch automated tests and collect results. But you shouldn’t need people to do this at all. Best practices today involves CI/CD practices, where automated software builds (nightly or other schedules) trigger automated testing. Not every test can be run for every build, but the full suite should be run for every build that will become a release.
For those tests that can’t be automated (and there are always some), junior engineers can do the job, but they are going to require training if they don’t have prior experience with testing (and if they do, they’re probably no longer junior-level engineers). If you just throw them at a device and a test-plan document, they’re not going to do it all right.
Apple may be doing all the right things here. I don’t know. This is just a response to the idea of “throwing bodies at the problem”.