![]() Until last year it would cut my battery life in half when compared to Chromium. Firefox has improved a lot over the past 2 years, but it was neglected on macOS for years. it's a bit too limited (I really need extensions).įor me, between Chromium and Firefox, Chromium-based browsers perform better on macOS. I don't use Safari because it's only available for Apple and to be honest. I use Brave as a "Chrome without Google" (no crypto stuff enabled) as main browser and Firefox (where extensions like uBlock Origin run very well) as secondary. But they also end up using less power than other browsers :P I guess one can say that they're "cheating" by degrading the experience a bit. I know Chromium started doing the same and apparently Firefox does it too, but I remember reading something about Chromium being less restrictive than Safari. Firefox or Chromium will still get the smaller VP9 or AV1 file, probably with a higher resolution, that uses the less efficient software decoding and is heavier on the CPU.Īnother thing that Safari used to do way harder than Chrome and Firefox was background tab throttling. In any case, there are a few things Safari does that will give it an "edge".įor example, if you have the battery setting optimise video streaming enabled, Safari will often get a H.264 file (sometimes with a lower resolution) that uses very efficient hardware decoding. I only received my M1 Max MBP last week and don't know if anything has changed. I was reporting my own experience with Intel Macs, but there are many articles online about this (some also say the contrary.). If Safari is good enough for you and you don't need cross platform support, then stick with it.ĭo you have any articles or numbers backing the battery life statements? I also use extensions like uBlock Origin, which can't run on Safari. I use macOS, Android, and Windows, so independently of how good Safari might be for someone that spends a lot of time away from a charger, it's not the best browser for me. With my usage, performance is better on Chrome, battery life is similar to Chrome and not as good as Safari, and like Safari, you may find the odd site that doesn't work well with it. Performance on macOS might be a bit worse than Safari and will use more power.įirefox is between Safari and Chrome in terms of extension support and probably the best option for privacy. Extension support is bad compared to Firefox or Chrome and since most sites are made for Chrome these days, you may find a site or two where not everything works well.Ĭhrome has more extensions, better site compatibility and better security, but isn't good for privacy. Safari has the best integration with Apple products and the best battery life. What's the issue Apple? The wireless network card on these machines not up to it? You know what they say once there are three machines with the same issue.It depends a lot on how you use your browser. Glad someone else is having this in some ways though - not just me going mad. Only if I'm on wifi does this issue creep in. I'm at a loss as trying to explain it seems like over-kill 99% of the time, but if I am doing a call and the only machine I have in front of me is the M1 Macbook Pro - I need to dial in on my phone to ensure I don't get kicked or have everyone else hearing a robotic version of me while I talk. ![]() It also doesn't seem to happen with Zoom or Skype. It doesn't do it on my Intel 16", nor does it do it on my Intel Mac Pro or iMacs I have available to use. This happens regardless of the Internet connection, home, office, coffee shop, tethering - you name it - I've tested it, all tests come down to it being an issue with the M1 Macbook Pro. As soon as I start to use other applications that need network traffic of any kind, that's when the trouble starts. ![]() With me: my calls are functional calls - as in - I'll be on one, and working during it to get conclusions, dig around and end the call when things are working again. In both options 1, 2 and 3 - I get the same results, no matter what I try. Keep that up during your calls to check what's happening when both the bandwidth and CPU usage rocket and start to cause issues. Triage leads me down this route, while on calls (you'll need to be using the Chrome App, or Chrome by itself) you can pull the Troubleshooting and Help window up In testing I have tried:Ĥ) Tested it w/ a wired Internet connection The strangest thing is, I'm having the same issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |