My case is basically this: When relying on optimized applications,
the M1 processor is an absolute champ when it comes to battery life and processor use, which is the
real reason this debate is coming up. No matter if I’m using Chrome-based browsers like
Vivaldi (which I recently wrote about) or Webkit-based browsers like Safari, the result is the same: processor use is kept in check, and memory consumption isn’t too much of an issue, because the operating system works around it.
What causes things to go off the rails, however, is when I use Intel-based apps, which seem to tax the processor significantly more. (And it reminds me of how web browsers alone were often enough to kick up the fans on my old machines.) To me, that suggests that a big reason this whole debate is coming up comes down to a problem with hardware optimization on Intel-based platforms, which is less purpose-built for the types of data commonly coming in from a browser—such as Javascript and encoding-dependent video.
On my older computers, I feel like the amount of battery life a particular browser allowed for was a major deciding factor in whether or not I actually used it. Safari was always the best, but it had such a paltry number of extensions that I never took it seriously. (Honestly, I still don’t. It’s to the point where I don’t understand why anyone would use it.) But the browsers with the most bells and whistles seemed to kill battery life way quicker.
But the M1 seems to allow for all-day battery life no matter which browser I use. Which means that the processor seems to be threatening to make the whole browser-resources-consumption debate obsolete.
That would be pretty amazing if it did. Let’s hope it kicks off a trend.
Now whether or not that happens, let’s remember that companies releasing graphs that rip on their competition obviously have a vested interest in making sure their offering looks the best. So, before looking at the numbers, make sure you consider the source.
Time limit given ⏲: 30 minutes
Time left on clock ⏲: 2 minutes, 43 seconds
Dig this issue? Let me know! (And make sure you tell others about MidRange!)