The days of assuming that Apple has the best chip efficiency are coming to an end, especially if the Windows/Qualcomm platform is a workable choice for your needs (maybe someday Linux support will get better).
Apple still has a lead but it’s small enough that it’s not a good reason to choose an Apple system on its own. The M1 MacBook systems got double the battery life of competitors, now 5 years later, Apple systems are at best getting ~10% better battery life than competitors, and some systems like the XPS 14 have Apple beat entirely.
Obviously getting 20 hours in real world productivity use was never realistic, and it’s not realistic on a MacBook Pro, either. I disagree that framework was “basically lying.” They live-streamed the laptop hitting 20 hours, it doesn’t matter that they changed settings to get there. MacBooks have a brightness slider, too. You aren’t getting anywhere close to 20 hours on a MacBook without turning the screen brightness down.
IIRC the MacBook Air/Pro can’t even make it to 20 hours regardless of settings.
The point is that the new framework 13 Pro laptop isn’t a 5-7 hour battery life experience like the previous models. Instead, you can expect 10+ hours depending on what you’re doing it, so it’s a full work day.
Standby time is likely also a major issue, unless Intel suddenly reversed course and decided to support proper sleep again.
Framework specifically has stated that they worked very hard to improve standby time and claim that it’s dramatically better. Being able to use LPDDR5x LP-CAMM2 modules aids in standby time significantly. We’ll find out soon when the first reviewers get their retail units in, probably within a month or so.
For standby time, my current framework 13 has never bothered me. It’s great that Macs have incredible standby but it’s much less of a dealbreaker than I originally thought it would be. I just have sleep to hibernate set up in Linux.
My system sleeps for 2 hours then hibernates afterward. If I am putting my system down for 2 hours I’m likely done using it for the day anyway.
Just take the L, dude.
To clarify for you, “moving the goalposts” means that I changed my definitions over time. You’ll notice that in my comments I never changed my definition of what it means to have good battery life. I know sometimes turns of phrase are easy to misuse so I hope that helps you out.
There’s no winner or loser here. We’re just discussing technology. I’d appreciate if you tried to add conversation value rather than just dissing me personally.
Panther Lake is an impressive chip. The only MacBook Pro that can achieve 20+ hours of battery life at all with any setting is the 16” model that comes with the largest battery capacity allowed on a commercial airplane. It’s really not framework’s achievement, it’s the chip that’s so good, and that’s great for consumers because you can find a lot of competition on the market that has the coveted “all day battery life” without compromising on performance.
I'm not sure it's fair to ding Framework specifically for not being able to make Linux battery life as good as Windows. Is that actually something they could reasonably fix?
My understanding is that the reason why Linux still struggles in this front is that nobody has put in the hardware-specific optimization work to make it happen. There’s also some friction with how the bulk of Linux dev attention is paid to servers rather than portable consumer hardware.
I am probably not competent to improve linux battery life myself (or at least I certainly don't have the time to get into that). But I can choose to spend my money on hardware and companies that explicitly support Linux, even if they aren't at the very top of the spec sheet. This has the best practical chance of convincing big-money companies and Linux kernel experts to actually spend time and money on this. Meanwhile, buying a Macbook and installing Linux on it is fine, I guess, but also invisible to the corporate world.