

Qualcomm’s stuff is within single-digit percentage points of the current-gen AMD and Intel chips both in power usage, performance, and battery life
Back in June, the new Snapdragon X processors were a lot more efficient than their x86 based counterparts. I can personally attest to much lower levels of heat generation.
The problem is that the current tradeoff is that huge amounts of the software you’ve been using just does not work, and a huge portion of it might NEVER work, because nobody is going to invest time in making it behave.
I agree with the sentiment, but IMO this is a PC and Windows problem. I would also extend this beyond pure comparability. I say this for a few reasons
- I lose about 5% charge/day with my laptop asleep. It does wake up very quickly, but 5%/day feels like a lot. At this point, I don’t think Microsoft has a strong incentive to really optimize the kernal for efficiency
- Historic massive variability in hardware across devices also makes it hard to optimize efficiency, although the current crop of snapdragon x laptops seem to have less variability
- One of the strengths of windows is that it can run applications written 20+ years ago fairly reliably. There’s a ton of software that’s still floating around that hasn’t been actively supported in years. I don’t see all of these software companies desiring to port their code over, especially without guarantees that the market will adopt ARM (the Apple approach) or until they see the ARM adoption rate go up (the current Windows approach)
All that said, I’ve had zero issues with emulation so far. I never personally used a M1 max when they launched, but from reports of that era the current Windows experience is at least as good as that.
We have a test environment but it’s a hot mess. All the data is made up and extremely low quality. All the things you would normally interface with are also in test, but getting other teams to coordinate testing in the test space is… a chore. We do the best we can with mock services, but without having real services or representative data some of the data pattern assumptions don’t play out. Leaders value writing code and our lack of architects that span teams mean that when team architects either don’t meet ahead of time, make assumptions, or don’t ever agree on a design then…
We always host UAT. We also track logins. Guess how many users even show up for UAT, let alone actually click on anything.
This is why the vast majority of our testing happens in prod when our users are doing real work.
Sorry for the baby rant :)