Readit NewsIt needs 30W at 4 cores 3.2Ghz. Ryzen needs around 5W per core but it's on a worse process. The entire system does use less power than a x86 system but that has nothing to do with the processor. It's more about how the SoC is arranged and that RAM is (almost) on the same package. It means they can get away with higher bandwidth and lower power consumption for the entire system.
The idea that it's all about the processor is completely wrong. Yet all we have heard is how fanboys cry it's going to be 3x faster than desktop CPUs because of misleading TDP numbers.
Apple is just jumping onto their existing ARM track, once they migrate their product line, which has surpassed Intel. Once they've migrated all their lines to ARM, the performance gains will be more like they have been on the iPhone/ iPad over the past few years. Mostly 20-30%/ year.
Back when the iPad Pro with the A10X came out, Apple claimed it was faster than half of all Laptops sold and people in the PC space were yamming on and on about how numbers don't show how much better x86 cpus are at 'desktop stuff' and that ARM cpus can't equal x86, even with the same thermal envelope and shouldn't ever be compared. Ironically, many are now stating that the reason why they are so good is because of ARM, which isn't true either lol.
Can Apple's M1X/M2 outperform desktop CPUs?
Qualcomm tried their hand at desktop CPUs with Microsoft a few years back. Is it time they tried again?
How comparable is a Surface Go with the performance/efficiency of M1?
Surface Go is nowhere close, half as fast in single core, 1/5th as fast in multicore. The 5W TDP is really a generic number with no real meaning as Intel doesn't really abide by it, I would say it probably uses about the same power as the M1, possibly much more under turbo while also having a much higher power floor (IE: When at idle the Surface go uses much more power)
Keep in mind that the Surface Go is very low-cost and the CPU is at a 14nm build.
You know the gap.
If you charge your phone every night it becomes a habit tied to your daily routine.
If you were to charge your phone every other night, you might lose track of what day you are on, not charge it and then the perceived battery life experience is worse. This is why smart watches with 3-4 days of battery have not prevailed over those with one heavy day of battery. They are annoying to know what day you are on so you might just charge it every night and if you do, the platform is trading off so much power that the experience is worse.
Plus, then you have to carry 2 days worth of battery or have half the power envelope as a laptop with one day. the concept all sounds great but the reality of people using things really has honed in on the fact that these things need to fit into habit and use cases that make sense.
The problem, at least for me, was the complexity of the model which makes the whole thing super scary when you've just started using it. That's where GUI tools come useful, as people are generally less scared of GUI tools - they make you feel there's less of chance of making a mistake because you put the trust in the tool to stop them doing something obviously stupid. However IME that trust is not really deserved as most of the GUI tools will just as happily let you mess up your repository...
I know Apple was trying to get to market quickly, but I fail to understand why we need Icestorm cores in a non-mobile CPU, especially with this already (really) low TDP.
Far more interesting to me is the idea that in heavy use, the Icestorm cores can run the OS, notifications and all that, allowing full uninterrupted use of the firestorm cores. Also when the mac is in idle it uses far less power.
Basically, I fail to see a reason to not keep them :).
I read this twice and I really don't have a single clue other than it having something to do with or requiring fast memory?