4 ms·
Apparently only Apple can get ecores working.
by spandextwins 3y ago
Apparently only Apple can get ecores working.
- rsynnott 3y agoApple had the advantage that heterogenous core setups coincided with a major architecture change, so third parties more or less had to change stuff _anyway_. Also arguably a different culture; your average Windows developer is accustomed to a status quo where you don't really _have_ to change anything; things will basically keep more or less working. Whereas Apple will quite happily break third party apps which don't keep up to date. You see something similar with HiDPI; within a year or two after Apple introducing HiDPI, it was rare to see third party problems with it, but most third party software never really worked with Microsoft's original attempt, and even their more Apple-like modern one is still quite poorly supported. (Interestingly, MacOS long had a hidden "smart" form of HiDPI quite similar to the old Windows one; used to show up in John Siracusa's MacOS reviews from long before the first HiDPI Macs. They presumably decided third party developers would struggle with it, and bypassed it for the fairly dumb pixel-doubling thing they use today, though).
- jshier 3y agoApple also has the advantage of reusing their ecores for other things, like the watch and HomePod mini. Does Intel reuse theirs for anything?
- nicolaslem 3y agoI am pretty sure it's the other way around, Intel reused their existing cores found in Atom CPUs and put them in their desktop lineup as e-cores.
- rsynnott 3y agoYeah, at time of introduction, Intel would have had a lot more experience of their e-cores than Apple. The e-cores in the M1 were, I believe, net-new and reused later (old Apple Watches just had process-shrunk former phone cores, I think).