3 ms·
I recently got an M1 mac myself and tried Safari out again -- I seldom used it on my 2016 Pro (preferred Firefox) but it's supposed to have stellar battery life
by Frondo 5y ago
I recently got an M1 mac myself and tried Safari out again -- I seldom used it on my 2016 Pro (preferred Firefox) but it's supposed to have stellar battery life, so why not give it a go?
Nice that they've got built-in tracking protection now, I guess, but I left Twitter running in a tab overnight and when I woke up Safari was reporting over a gb of memory use for that tab alone. Something in how they cache or handle JS for some of these long-running services, or maybe having to do with service workers ?, Safari just seems to consume a lot of memory. It's not a huge issue I guess, with the way the M1 never seems to have any memory pressure issues, but it's part of why I remember switching off Safari in the first place.
If anyone knows why Safari seems to consume more memory with these long-running processes, I'd be real curious to know why...
- spurgu 5y agoBattery life has been the reason for me trying it in the past as well. And yeah I mean even though Activity Monitor is reporting high RAM usage I don't seem to have any memory pressure issues so it might not be that big of a deal (MBP 2015 w/ 8 GB RAM). I'm actually considering getting an M1 myself next week. Have been waiting for the initial kinks to get sorted out and most apps ported to it and I think it's time now. :) SSD wear seems to have been resolved with the latest Big Sur versions and fewer Rosetta apps and now even ST4 beta has an M1 build. My justifications are that I'll get an excuse to upgrade to 16 GB RAM and I'll get touch ID so I can have a more secure password and not have to type it all the time. And with the stellar performance and battery life of the M1 I can just keep using Chrome (Brave). :P