Because the G5, while awesome in performance, would have needed a giant enclosure for all the heat IBM didn't care about.Why did we ever adopt Intel in the first place?
Because the G5, while awesome in performance, would have needed a giant enclosure for all the heat IBM didn't care about.Why did we ever adopt Intel in the first place?
For those nice Intel stickers?Why did we ever adopt Intel in the first place?
Yeah we were never going to get the PowerBook G5. Sad.Because the G5, while awesome in performance, would have needed a giant enclosure for all the heat IBM didn't care about.
I’m able to get safari 14 on Catalina, but maybe that’s just because it was released separately from (and earlier than) Big Sur. I’m holding off for comparability reasons in work though.Or if I want to open an Apple News link without it opening in the News app. That's irritating.
But yeah, Safari has always been the most efficient and my default. Biggest gripe is not being able to update without updating the OS, and since my machines are on Mojave still, quite a few things don't work in Safari now.
What about the comparison with the Ryzen?So this primarily shows how much speed improvement native code will get you. Doesn’t say anything about M1 vs intel. It’s more native vs Rosetta.
D'oh. Standalone Safari updates, I don't remember that!The latest safari 14 runs on Mojave.
Apple couldn't make their own CPUs back then. The M1 comes after years of iterating on iPhone performance.Why did we ever adopt Intel in the first place?
Because Motorola.Why did we ever adopt Intel in the first place?
https://support.apple.com/downloads/safari. I'm confused, why can't you download directly?120%. Safari's biggest short coming is the OS update.
I had a very difficult time reading this...Because appke dud nit have the m1 chipmat the time, and IBM was moving to slow for apple, larly Intel has been having problems with keeping to their roadmap and apAppke has had such sucess with its in house phobe/ tablet chips that they decide to do a desktop chip fir them selves ( vell kaptop for rhe moment) and they seam to have managed it quite well
Or maybe google finally got it right for the M1, and is not there yet on x86?I'd say it's the other way round.
Given that Rosetta2 does not translate at run time and is known to be relative good at replacing x86 code with the same functionality in ARM/-Silicon as shown by Geekbench just going native would give you only 20-40%.
So what did happen here is that the binary is optimized for the M1 and the only question is wether that was done by hand or just compiler-magic (I'd put my money on the later).
As such improvements will be all over the place depending how good a fit the task at hand is for features offered by the CPU(SoC).
Something that just does lots of branchy single thread integer code might still be faster on Intel, while ML code that used to run on the CPU will be magnitudes faster running on the dedicated ML-cores.
Ditto. Hopping between Safari and Brave.#TeamSafari
(Or Brave is something is broken in Safari)
https://support.apple.com/downloads/safari. I'm confused, why can't you download directly?Or if I want to open an Apple News link without it opening in the News app. That's irritating.
But yeah, Safari has always been the most efficient and my default. Biggest gripe is not being able to update without updating the OS, and since my machines are on Mojave still, quite a few things don't work in Safari now.
In other words, avoid Rosetta 2 to avoid nearly 50% performance penalty. All apps should ideally be native.
D'oh. Standalone Safari updates, I don't remember that!
But now I remember the issue with Safari, they killed uBlock Origin in the new versions. Now I have to use AdGuard, which isn't as good.
The benchmarks in the article include a Ryzen (Windows on Intel) benchmark. The Ryzen results barely beat the Rosetta on M1 results and lagged well behind the native M1 results. So it does not appear that JIT is a significant factor.This is probably because Chrome does Just In Time compilation of JavaScript, which Rosetta obviously can't translate ahead of time. So it's expected that browsers and Electron apps suffer more in Rosetta than native ones.