PS: 4 hours on Air M1
So, roughly assuming that you could compile WebKit 10 times before the laptop runs out of juice, that'd give you 4 hours 10 minutes of battery life.
-----
[1] https://techcrunch.com/2020/11/17/yeah-apples-m1-macbook-pro...
On the flip side, you get 8 full fat cores instead of 4 fast & 4 not so fast, so your compile jobs might go a bit quicker. Have to wait for the benchmarks to find out for sure.
Compiles that use multiple cores with end significantly faster and thus battery life will be compensated.
I have some Android friends who are super happy with their phones. When they ask why I’m upgrading my iPhone again and I say “it’s got a lot better performance” they usually say something like “why do you need a faster phone....my midrange 3 year old android phone is blazingly fast”.
It’s not until we lift all users in general that we will be able to create new and innovative software. I like to compare an old school project where they had to create a spell checker...but this was back when you didn’t have enough ram to keep the dictionary in memory.
More memory and faster CPUs make yesterday’s challenges trivial for today’s developers.
Otherwise, I don't really see the point. Every machine has a different purpose.
My telephone is for phone calls, texting, extremely light emailing, checking weather, using it as a GPS, occasionally taking a photo or a quick video.
My Surface Book 3 is for actual on-the-road document work, programming, light gaming, and digital painting.
My Ryzen Threadripper / RTX 3090 workstation at home is for no-shit, actual income-generating work and super-heavy-duty gaming.
My Panasonic Lumix DC-S1H is for videography, but my Canon EOS R5 is for highest-quality stills, and my Sony A7C is for travelling.
Every one of those cameras has different purposes, different use cases. Just like the rest of my hardware. There is no "one size fits all" anywhere, for anything.
> More memory and faster CPUs make yesterday’s challenges trivial for today’s developers.
Today's developers are by-and-large utter shit at designing software. Its usually poorly thought-out, poorly-documented, and poorly-maintained. The number of truly exceptional software programs out there is incredibly sparse.
Yes, there aren't a lot of valid reasons to spend over ~200 Euro for a phone these days (unless you're tech enthusiast).
I suspect a mix of Wirth's Law plus a lower level of polish on things like drivers on cheaper phones (inexplicably poor WiFi stability, for example)
But recently my friend bought a Motorola for 200 Euro - Snapdragon 730, 6 GB RAM, 128 GB UFS 2.1 storage, pretty good main camera + (so-so) ultrawide, (gimmicky) macro camera, 5000 mAh battery. I was very impressed what can 200 Euro these days buy. I'm pretty confident this phone will do just fine in 2 years too ...
Large numbers of people use their phones for games, video/photo editing, videoconferencing (which can involve real time image processing for virtual backgrounds and appearance filters).
At the low end of the phone market, phone hardware performs significantly better today than it did two years ago for those tasks.
Realtime img processing is an interesting one. I dont see any precedent that that's a big usecase, most people just set and forget zoom calls but you've brought up a good feature.