Not look too bad best to say.

Even if we add a one node advantage, we still have a ~15 watt chip making 20W-30W chips sweat.

If you downclock Zen 3 to match 15W TDP, you may well get M1 beating it by double digit margin.

M1 is simply a way more efficient chip than any X86 chip can be because of 40 years of architectural advantage.

- latest x86 chips have patently gigantic decoders metastasising into backend. They are very tightly coupled to pretty much every other piece of logic.

- x86 memory model, and blockage behaviour costing huge transistor count to work around

- better SMP efficiency because of laxer memory model, and SMP logic being deeper integrated into cores, rather than being an afterthought

- generally better register utilisation, at lower transistor count, and the upstream software ecosystem historically having better understanding how to work with large register count

- X86 cores prefetch from both main memory, and in between caches is more expensive, and less efficient because it has to rely on more complex logic, and do more guesswork than in ARM.

The list can go on for a few more screens.

Remember. Even if M1 is a SoC, it still manages to beat Ryzen which barely have much besides cores, memory controller, PCIE, and USB. If you give a 1 node handycap to Ryzen, and only compare cores, you will still get M1 having almost 3 to 4 times advantage at performance per square mm.

It's really sad to see X86 development digging itself into a ditch with "40 years binary compatibility at any cost."

With all regards to Su Lisa, I believe they very much understand all that, but nevertheless still signed under the idea that X86 market will never go anywhere.

I believe it's trivial for both AMD, and Intel to easily slash X86 transistor counts, while increasing the performance by double digits if they can go in err of the X86 ISA convention on just the few most egregious anachronisms.

Nah, people have done that experiment and it is competitive

40 years of architectural advantage is X86 electing to forego results of 40 years of advances, and improvements that every other sane ISA had, and instead trying to add them by increasingly complex "workarounds."

Giant transistors counts go to allow X86 cores to not to break ISA compatibility with a 40 years old chip, while trying make new ISA features to live along with it.

Their commercial demise had nothing to do with their hardware.

Oh come on. You’re making it sound like a toy computer that’s nice for little Debbie who can now watch YouTube videos a little faster.

While my MacBook Air is unplugged, I can edit 4K video in full frame rate for hours and it doesn’t even get warm, let alone hot.

In multicore workloads Zen 3 slaps the M1 even per watt.

5800U (Zen 3 mobile) and M1 are actually very close multithread perf wise despite one being a 8 core part and the other a 4+4 part. And with more power use for Zen 3 too.

What hurts Zen 3 there is while the M1 maintains the full clock with all cores busy, Zen 3 has to downclock away from its max turbo clocks.

The 5800u is a 15w part, you might be confusing the normal part with some overclocked implementation.

But the 5800u at 15w is still faster than the M1 in multicore.

Yes, Zen has to downclock, but it has more cores.

Trying to find with one of the best 5800U scores: https://browser.geekbench.com/v5/cpu/compare/7449909?baselin...

It's for 5800H which is at 45W where Ryzen can get a tiny edge.

On Cinebench, the 5800U gets much more than the M1 in multicore and slightly more in single core. It even edges out the M1 on Geekbench, though Gb is a poor benchmark.

Cinema 4D, the program that Cinebench benchmarks, normally does the renders on NVIDIA GPUs, not CPUs. As such, it’s a very poor benchmark.

And those 5800U results are at probably much higher than 15W. (Because that’s the base config, OEMs are free to ship with higher TDPs)

Geekbench in general has very heavily biased for ARM as it does not run the same code on both. Cinebench doesn't have this issue. And while yes nowadays a lot of rendering is done on GPUs for C4D the class of programs is path-tracers and they are often ran on CPUs for many scenes.

> The M1 is also ran at much more than 15W in some models.

Nope, it's the same M1 for both, same voltage/frequency curves and top clocks. It's the whole point of having a chip that's named the same. '

No modern laptop CPU has a headline power use number. They all try to use the headroom that they've been given.

Cinebench is very far from being the end-all of benchmarking that you say it is here. And there are far more optimised renderers around if you want to benchmark that. (RTX makes the matter moot nowadays anyway)

It does not use AVX-512, or older AVX levels much for that matter, for a workload that is SIMD-friendly. For Arm, they leave lots of perf on the table too. (Cinebench uses Intel's Embree renderer, with AVX-512 disabled)

Geekbench 5 is designed to be a composite index of multiple benchmarks to be more realistic to some extent than using just one. You can also access to the scores of the subtests too.

Probably some of that is because they did try to do something different once - and Itanium was an unmitigated disaster.

400%? Do you have any sources to back up this somewhat extraordinary claim?

And 119 mm² total die area claim

For Zen 3 I used https://cdn.wccftech.com/wp-content/uploads/2020/11/AMD-Ryze...

0.5mm² per core on M1 vs 2.2mm² on Zen 3 sans caches

If you add caches, it gets much worse

17.5mm² vs 65mm²

And I may have had inadvertently included non-core parts into M1 calculation because of no official die floor map

What does this mean?

"Didn't look, too bad" might be a mode of "buyer beware" -- if you are not careful at the market, nyou might come home with trash.

It's still a tiny percentage of the area. The caches are the biggest.

[1] Well, mostly. There is such a thing as static power draw, but I suspect that the transistors in the L3 cache are optimized to have lower static leakage than the transistors in the core logic, which are optimized to be fast.

I repeat my stance that x86 instruction decoding is a tiny part of a processor, and things like vector units (which are also often powered down when idle) and reordering logic take far more power.

There's a paper about this that compares the efficiency of different ISAs, and basically concludes that ARM and x86 are no different in that respect. Only MIPS is an awful outlier.

https://www.extremetech.com/extreme/188396-the-final-isa-sho...

My previous laptop was a 2016 MBP with an i7, and the M1 destroys it. I can build large projects like LLVM or WebKit fast and it doesn’t even get hot.

I’ve also been running Linux VMs with the new Parallels and they feel native speed.

Rosetta 2 is incredible, Intel apps are very responsive on M1.

My work computer is a high end 16” 2019 MBP with 64 GB of RAM and honestly if it weren’t for needing the extra RAM or the occasional x86 VM I’d trade it in for an M1 in a heartbeat.

I’ll agree the Apple hype is unrealistic at times, but the M1 is one that absolutely deserves it.

You would need to benchmark it against a current chip from someone else.

I think people are a little too nostalgic when talking about Apple build quality. There's a 2011 MBP here that still works well. But recent releases... no better than the competition really.

I considered that keyboard to be designed to fail. I'm not interested in gambling that another component won't fail the same way. It's easier to use products that have not demonstrated such designed failures.

The good news however is that due to this garbage tier engineering I've discovered that desktop Linux is more stable for me than post-Catalina OSX - I'd have probably never found this out otherwise.

It's pretty clear what happened, and it's unfortunate but banal: someone went too far with making the key mechanism as thin as possible, and all plastic to make it easier to manufacture. Ends up the plastic wasn't strong enough for the little pins in the mechanism.

That's it. Just an ordinary design mistake. Embarrassing but no conspiracy.

FWIW they've resolved it. The keyboard on this M1 MBA is perfectly fine.

I see it as a symptom of the Jony Ive ideology, untethered from realty by Jobs, poisoning Apple in the early 2010s. iOS7 flat UI, overthin devices, keyboards.

Signs are pointing that Apple is recovering from this (new aTV remote).

https://finance.yahoo.com/quote/AAPL

I don't see any evidence that Apple's stock price was affected. Apple can ship any garbage (they shipped a keyboard they knew was defective for three years) and people will buy it because they're locked in to Apple's services, another reason they're pushing services so hard at the expense of the rest of the company.

Given that you know the keyboard has been fixed, is there a reason why you didn’t make it clear that you were talking about older machines and not current ones?

You make it sound like the current machines have the flawed keyboard, which is not true as far as I am aware.

Coming from lifelong Linux-land it's actually comical reflecting on how poor these things operate in day to day. The most prominent issue for me is how poorly they operate with my USB-type C dock I use for multi-monitor.

(Honestly I never even noticed that the apple touchpad was better than any other touchpad, but I understand that touchpad users will notice things I didn't.)

If a product fails within the first 10% of expected lifespan I'm no longer interested in that product. If it fails _AND_ the manufacturer refuses to take responsibility until months of bad press and class action lawsuits then I'd have to be insane to trust them with another device.

It's a different keyboard. Different mechanism, very different feel, larger key travel, much more comfortable.

I have a 2018 i7 MBP and a 2020 M1. The keyboards feel incredibly different. On top of that the 2020 M1 has a real Escape key which is a huge upgrade for anyone in unix land/developer land, etc..

The 2019+ keyboard has had no controversy or reputation for failing.

My 2018 one does feel like it's on it's last legs FWIW. It's a work machine.. just hoping to get a refresh before it dies.

edit: form factor, performance, build quality.. is also up there, I just didn't mention it, because I think the battery life is the killer feature of the M1.

Check out Chrome build time benchmarks between 3/4xxx and 5xxx series (or any dev tool related benchmarks). 10-20% off your iteration cycle is noticeable - and that's a single generation jump.

Increasing iteration speed is a big productivity boosts, seeing professionals with 5+ year old devices is just ridiculous to me, you spend 8+ hours on that device - investing 2000$ for an upgrade every two years is not that much to ask.

Compiling Chrome is a nice benchmark but in reality dev cycles are quite smaller (or you might want to optimize your toolchain).

Finally, it's quite common for developers to forget the kind of hardware their users are running on. Then they produce software that only runs well on the next gen hardware. If you develop on a beast, then at least test whatever you are producing on a 3-4 year old machine to see how it will work for the clients.

I have a 2014 retina iMac. At some point in the next few years, I’ll probably replace it with an M series iMac, and then put Linux on it. It’s hard to imagine that it will ever really reach end of life due to speed at that point.

I’m not sure why Lenovo doesn’t use better IPS panels, they can’t be saving that much margin from them.

That’s one of the highest end ThinkPads though, so I guess that’s to be expected. Have heard that getting a good panel on more mainstream models like the T-series can be tough.

The main bottleneck is the production capacity, we badly need more manufacturers of high end chipsets.

But do you think that Apple stopped innovating after releasing the M1 last year? Don't you think the M2 (or M1X whatever it's called) is well into design and prototyping at this point?

Just because it matters on Android, which is a COMPLETELY different system, doesn't mean it matters as much on iOS.

Yes, it matters a bit when switching between multiple apps, but app suspend is handled in a completely different way on iOS than on Android.

Apples to Oranges.

Eh, I'm not sure that's true. They did with the original PPC, and also the G3 and G5.

It's difficult to compare the Apple Silicon versus PowerPC, because the new Apple hardware is far more ambitious, the whole platform. I would expect that the memory SSD controllers are to some degree licensed from other industry players. The CPU architecture is something else again. Issues eight instructions per clock -- per core. The M1 core design has more in common with IBM mainframe POWER9 than with a typical x86 core. It's remarkable to see this design ina low end consumer device. A mobile.

There have been just so many genuine tech news articles of the form, "Future Apple Competitor Product Beats Current, Widely Successful Apple Product".

It's the twin brother of all the "Currently, successful Apple product feature technically existed on [not-Apple] Product years ago (even though basically nobody used it)."

People read those articles and conclude it's all marketing hype but never ask themselves why it seems to happen again and again where simply checking off the box for having a specific feature never seems to actually lead to broad adoption. And if it truly is ONLY marketing hype leading to those ecosystem effects, then maybe you should start thinking of marketing hype as a feature?

I see what you did there. Really casting shade on Intel!

I can answer why _I_ downvoted the comment. It was this part:

> [...] it's really surprising to me how many eagerly lap up the angle Apple is pushing without much reflection, even on HN. Like the good old Apple hype days.

You can make a point without implying that anybody who doesn't agree with you is incompetent (the "Apple hype" meme is really stale).

Chips like the M1 (or ideally, something similar made available to other device manufacturers) is still really interesting. The ARM architecture can scale down better than x86/x64 can, allowing a device maker to hit low end performance targets with less cost than x86 chips can manage. For the low end, it also tends to provide better power consumption for a fixed performance target than the x86 offerings.

This makes M1 type chips really interesting for any manufacturer who want to make devices that span a huge scale of performance requirements, from slow kiosks performance range to the decent laptop range. All being the same ISA makes sharing firmware and applications across the lineup easier than having to switch to x86/x64 above some threshold.

It also does not hurt that M1 means that the really popular for development Apple devices are now running on ARM, which helps ensure that more software has been ported to (and/or tested on) ARM devices. ARM's weak memory model for example is something that can trip up a lot of software that tries to implement low lock algorithms, but whose designers were only familiar with the x86/x64 memory model.

This is purely theoretical. Apple will <<never>> sell its chips to other companies.

So if you were expecting Apple Silicon on its own to start a revolution, that's never going to happen.

Microsoft already have a Surface product with an ARM chip that didn't get updated in this round AFAIK. It already has solid ARM performance, but it's not as good as M1. It was let down with how well x86 emulation worked, but there seem to have been improvements including x64 support. If they focused on improvements with the chip design then they could see improvements along the lines of Apple. It's a question of whether the investment is made rather than whether it's possible.

The team that built the M1 is a collection of top tier ASIC designers that came from several acquisitions, from PA Semi forward. The Qualcomms and Caviums and so on just aren't in the same league. Lord spare me another tarball of garbage and random kernel patches called an "SDK." They don't really have the same bench and don't pay top dollar and it shows.

It is unlikely that there will be an M1 equivalent from any of those guys. Intel? AMD? Absolutely.

Back in the 90s, when Jobs was gone, Apple licensed its OS and almost went bankrupt as you could simply get a cheaper clone of Apple's computers with the OS on them. They won't repeat that mistake again.

Also, saying that people are "lapping up" the Apple marketing suggests that it's more sizzle than steak. But it's completely undeniable that the A chips, and by extension, the M1 is a beast.

Reasonably close only counts in horseshoes and hand grenades. Until a 5nm version of the AMD stuff can run MacOS, there’s no point comparing the 2.

If the AMD stuff blows past the M1 (or the M-whatever), Apple’s marketing will turn on a dime.

So no, the Ryzen 5000 with 5nm would NOT level the field.

I mean, this is _kind_ of true, but it's not unique to Objective C, the M1, or even particularly intentional. The _ARM_ memory model is more conducive to reference counting in general than the x86 one. Nothing special about Apple's chip in that respect, tho.

So does every other Intel & AMD laptop CPU from the last 5+ years. So does every Qualcomm SoC from the last 5+ years. This has been incredibly common for years and years now.

This does a lot less than you think it does, particularly since there's very few consumer workloads that switch between CPU & GPU.

Overwhelming majority of MacOS/iOS software is written on Obj C and Swift, which have the same underlying semantics.

That said ARC doesn't have such a great impact on performance as some people (esp. fans of Java's GC etc.) would convince you. Most ++/-- operations on the refcount are eliminated by the compiler.

https://github.com/ixy-languages/ixy-languages

So they made the only sensible decision, and just like Microsoft did with COM, they added support to the Objective-C compiler to automate retain/release messages in OS X Frameworks.

Naturally being Apple, that pivot had to be sold in a way that the reason was being of RC being better and not because of the technical failure to have a tracing GC in Objective-C , while remaining compatible with C memory model.

Apparently, moving the GC document with all its caveats regarding possible programming issues, out of search index also helps to keep the story as well.

https://developer.apple.com/library/archive/documentation/Co...

There is of course a GC language on iOS (JavaScript) but expensive webpages get killed quickly.

It's not unavoidable, but Swift doesn't give good tools for avoiding ARC-based performance cliffs, so it takes a lot of profiling and effort compared to other languages.

It’s the first time in a over a decade I’ve felt a revolutionary step forward in a chip and the only time it has ever come with less power.

Process node is a factor but I find it hard to believe it’s the only factor. I know enough about the X86 legacy tax to know that is not the case.

Apple didn’t do black magic. They just took a cleaner superior CPU architecture and made a desktop class muscular chip with it. Other ARM manufacturers could equal or exceed the M1 if they wanted. X86 has been delivered a death sentence.

IMHO the greatest threat to AMD is ARM not Intel, and vice versa.

I see lots of people saying "If only $company had an ARM device", and I don't understand it. My experience of ARM device is slow laggy janky products - from competing smartphones, tablets, router and network device management interfaces, year on year, the pairing is always (arm + fucking slow).

It's only Apple who have managed to get "desktop class" performance, and at this point I'm more willing to attribute that to Apple doing black magic than to ARM being inherently superior.

Microsoft have piles of money, thousands of developers, they make hardware, they've been working with ARM since the likes of the Compaq IPAQ PDA and Windows CE 21 years ago, and the Surface RT in 2012, their ARM devices are nothing to speak of. Google, industry gorilla of tech with the finances to match - see the famous Gruber/DaringFireball about iPhones far ahead in single core JavaScript performance year after year after year. Tech giants like Samsung, Qualcomm, Sony, who have been designing and building chips for decades, with their own drivers, firmware, and customized Android builds, and building their own flagship products.

Apple whomps in from "nowhere" with the fastest ARM device anyone has ever seen, and the critics response is "anyone could do that if they wanted to".

Then why don't they want to?

[Edit: Consider also that Apple spent $278M on acquiring PA Semi chip design company in 2008, and $600M on Dialog Semiconductor in 2018, and Microsoft spent $2.5BN on Minecraft. I say these companies "are tech giants with finances to match", but it's not like Apple had to lean hard into their hundreds of billions cash pile to do what they've done. Instead they had to do something that appears to be "black magic" (i.e. desire + leadership + execution + long term planning + ???)].

> Apple whomps in from "nowhere" with the fastest ARM device anyone has ever seen

Not really from nowhere; they've already had the fastest (non-datacenter) ARM chips anyone has ever seen, fairly consistently, in their phones, for years.

The first A-series chip they officially released and named was the A4 in March 2010. That is 11 years ago. That is the beginning of M1. And the reason is originally in this amazing Ars Technica article [1]. Apple has always wanted to fully control the entire stack.

Any competitors in the same space lack either the vision, or the products, or the money to do the same thing. In the case of Microsoft and Google, their internal politics don't allow them to do the same thing (Google couldn't care less about hardware because the Web is where Google's money at; MS cares about hardware but traditionally they have relied on throwing money at partners to make them come up with solutions).

[1] Owning the stack: The legal war to control the smartphone platform, https://arstechnica.com/tech-policy/2011/09/owning-the-stack...

One of the ways we already know that beefy ARM processors can work well (and with better power efficiency than Intel CPUs) for heavier workloads/at higher scale than mobile or embedded devices is that it's already being done in the server space. Is scaling ARM processors up for the desktop radically different? (If so, I'd love to learn a bit about how )

The problem that remains for anyone who wants to sell PCs with something other than x86 is that desktop users want their apps, and for Windows users those apps are distributed as x86 binaries, and users aren't in control of that (especially for unmaintained or legacy software). Software publishers won't build or optimize for a new architecture if they suspect it's just going to be a flash in the pan, and this creates a chicken-and-egg problem.

But Apple can just declare that their new architecture is the only option for you if you're buying a new Mac, and a ton of their users will come with them no matter what. App publishers will just deal with it, knowing that they have to play along if they want their application to have a first-class experience on Mac. This is a huge deal, and not a position any particular PC manufacturer could hope to be in!

I'm sure Apple has done lots of technically impressive stuff that I'm not even competent to really appreciate in order to make this architecture change happen. But other vendors are more capable of technically impressive stuff than they are of forcing adoption for enough users to reach critical mass to get people who sell/distribute proprietary software to come along with them.

Apple is in a position where it can move swiftly and decisively. They have an army of software engineers who can port Apple's OS and associated Apps to a new architecture. They can force their entire ecosystem to move to a new architecture, and are emboldened by the fact that they've done it twice in the past (the first time they were more hesitant).

If Samsung wanted to pull down the latest Qualcomm ARM chip, slap a Macbook-sized heatsink on it, and go head-to-head with Wintel and Apple, they would fail. What are you gonna run? Linux? Some abortive version of Windows on ARM that doesn't support the vast number of x86 apps?

Even ChromeOS is missing barebones necessities like Photoshop, so professionals won't touch it. So the ChromeOS market is doomed (at present) to have "thin & light" and "long battery life" as it's only selling point.

I think we'll see M1-style ARM devices come out of the woodwork in 2021-2022, running ARM Windows and Linux and ChromeOS, simply to attempt to copy Apple. But I don't think they'll be as successful, simply because the apps aren't there, and no one can force developers to port to the new architecture as Apple can.

Thing about your comment is "Who would buy it" assumes it's basically the same and people are indifferent. My griping is assuming ARM is generally worse. But if we take this alternate world seriously then the reason for ARM is superior performance, so the answer to "who would buy it" and "why would developers switch" is driven by that - like when Apple was falling behind with PowerPC - it wouldn't be Microsoft pushing it on an unwanting market, it would be a demanding market pulling it with demand.

If Samsung could push a better-than-Intel chip, would Microsoft not want a piece of it?

If Samsung Chromebooks were suddenly more powerful than an Intel i7, would developers not sit up and take notice?

My contention is they can't, because ARM isn't that different, and it's Apple's black magic that is the real difference.

I remember the jump from the 486 chips to the Pentium being that dramatic. Heck, 486DX2-66 to P100 brought Linux kernel compile times from 45 minutes down to like 5 minutes.

Back then, I think a big part of these jumps wasn't just CPU design. I think a lot of it was that those CPU design changes were often accompanied by massive improvements to overall system architecture. So the I/O buses, memory, peripherals, all of it got a lot faster as part of the same upgrade.

Last time it felt like there was a jump this big was around 2005-2006 when the Core 2 Duo started becoming common.

Is it really a gamechanger for surfing, coding, videos, etc?

Curious because I might grab the base mac mini 8gb for music production, surfing, Java coding etc.

Also you said music production so verify before hand that your DAW, etc of choice will work fine. I use Reason and the visuals in the DAW itself are still laggy, but it isn't M1 native yet.

Other things like the fact that World of Warcraft runs at medium settings on a 1440P monitor feel kinda magical given I can barely feel any heat leaving the M1 Mini.

In the end I returned my M1 Mini (8gb/256gb) because my personal experience still felt half baked at this time. Once we hit the next generation a lot more software will have caught up.

Apple's memory and storage options tend to always be on the disappointing side.

The impressive thing about the M1 isn't just raw performance but performance / watt. There are obviously faster high-end many-core x86 chips, but the power use difference is wider than the speed difference. The M1 destroys mid-range Intel and AMD offerings at a fraction of the power consumption.

Check out this madness:

https://browser.geekbench.com/mac-benchmarks

The MacBook Air trounces the top-end Mac Pro on single core performance. No this is not the top-end Intel you can get, nor is it as fast as AMD, but it's a MacBook Air and consumes a small fraction of the power.

Again... the power efficiency is the thing that really blows me away. 5nm accounts for only some of that.

On multi-core the same MacBook Air is just below recent Mac Pro models on total computational throughput. To beat the MacBook Air you have to go up to newer-generation Xeon chips with 8 full-speed cores. The Xeon is branded as a server chip and uses as much power as probably eight to ten M1s.

It's just insane. If Apple puts, say, 16 full-speed core in one of these chips it's absolutely over for all other vendors. Speculation is that the 16" Pro will end up getting 8 performance cores and 4 low-power cores. I wouldn't be surprised if it ends up beating the top-end Intel Mac Pro.

I'm not sure that they can easily add more cores to the M1. If they can, that would also raise the TDP. And adding more cores does not increase performance linearly, even if the architecture is made for it.

Also keep in mind that comparing it to 14nm Intel processors with an architecture from a decade ago is a fair comparison when comparing M1 vs prior Apple products, but is not a fair comparison when comparing it against what x86 can do in general. You would need a modern x86 processor targeting the same watt usage to have a completely valid comparison. As discussed in the thread above.

So yeah, it's a great processor for its target. And it likely will also be a very strong processor when scaled up - it bodes well for the future of ARM. But don't extrapolate the performance too linearly, that is likely to be misleading.

I expected the M1 to be like a much lower power and maybe a bit faster version of this chip, and was really blown away by it being far beyond that.

Heck, he might have used an old dual core with an HDD from all we know. Of course the new M1 models would make a big difference then. So would all other modern laptops.

But in that context of x86 and ARM Zen3 is absolutely the only sound comparison.

I would have some sympathy with that - but that's not the same as discounting the parent's perspective because Apple somehow weren't using "modern processors" previously - because that simply isn't true.

And I still think it's very valid to not forget how old hardware used for subjective comparisons will be. E.g. the old Macbook air sold very well all that time.

It's likely the M1 is better in that category, but it does not look like a huge difference if you factor in the higher performance you get from the Ryzen 9 5980HS.

Multi core better but still lower but not too surprised as it's got 8 large cores vs big.LITTLE 4/4 for M1 - not clear when those cores will start throttling down.

Suspect single core performance is what drives apparent responsiveness so I'd say not too surprising that the M1 gets rave reviews from users.

With my 2400G the benchmark takes 5.5 seconds. With someones M1 it takes 1.3 seconds.

We still need to verify that was run at the same settings, but it looks like the M1 is going to be faster than the 5000 series APUs regardless, possibly by a large margin and I'm assuming the 5000s are between 1.4x and 2.0x the speed of the older 2400G.

It will still be interesting to see AMD on a 5nm process, and Zen 4, and with 8 core, but by then Apple will probably have an M2 on the 3nm process. You gotta compare what can be obtained today.

The 5800H gets 2.5x on cpu benchmark's rating vs the 2400G. This is composed of a 50% single core and 300% multi-core improvement.

2400G: https://www.cpubenchmark.net/cpu.php?cpu=AMD+Ryzen+5+2400G&i...

5800H: https://www.cpubenchmark.net/cpu.php?cpu=AMD+Ryzen+5+2400G&i...

That's in large part because its 8 cores instead of 4. The test I ran makes good use of multicore, but going from 4 to 8 won't cut the time completely in half. I suspect the M1 will still beat it by a bit.

I take back my comment on availability. We ideally need to compare things on the same process node to see which design team has done a better job ;-)

AMD’s 5nm shift is scheduled for 2022

iPhone 13 (2021) rumors indicate a 4nm SoC

Option two would just be to make an A15 be only a die shrink and surprise ! It fits.

The whole article is about not having to choose between performance and powerusage. With "5000", which 5000 do you mean? A 100W cpu of about the full cost of a macmini?

This is the whole point of the article. Apple made a monster move. Next up: Apple Cloud. M1 based cloud computing. Will save them a couple billion per year on aws which expires in '22 or '23 iirc.

I thought the company would wait and deploy a later gen chip. Though with the standardization of M1 across such a wide array of products makes me think it is going to be the M1.

So I had thought there may be something learned in the mass deployment that would trigger even minor design changes.

Perhaps those are software issues. Or maybe the M1 as a product name should not be taken literally to describe the SoC in the current lineup.

We know the Secure Enclave component appears to have been updated mid-production this past fall for a host of A-series chips.

Perhaps, if light changes were needed Apple would not see them a sufficient to designate a new moniker.

Or perhaps they are but the iMac and (theoretical) apple silicon-based data centers are intending to build consumer confidence in this bold foray.

https://9to5mac.com/2021/04/12/apple-security-a12-and-s5-pro...

Also do you know how many machines it would take to outfit a reasonable demonstration scale facility?

Is that number so large that it constrains the ability to just go that much further?

(Hint: we do)

And for 5nm, I'm quite sure AMD already has contracts for that with TSMC. So the gap should be even smaller.

It’s not that it doesn’t matter at all, it’s just that it matters a lot less once you’ve checked boxes like that. The effective experience of both would be “you only need to charge it overnight”

The same can't be said for the MBPs I've owned over the past decade. They get ok battery life but I always needed to know where the nearest outlet was. While an 11 hour Ryzen might be close to a 13 hour MBA, those extra two hours is the difference between a full weekend worth of work or just a full day.

For anyone wanting long battery life in a laptop those extra couple hours are important.

On the other hand, I think if you can go a full day on a battery, that should be enough. You won't be using your laptop for 20 straight hours.

The 7nm Ryzen 5000 mobile chips are not very power hungry either.

https://www.anandtech.com/show/16446/amd-ryzen-9-5980hs-ceza...

https://www.youtube.com/watch?v=r5bAMoQt7EQ

- With M1, Apple has finally closed the loop and created a fully closed system that it has control over vs an x86-64 platform that is more open and gives us users more choice and control.

- All new devices with M1 SoC score very poorly on repairability and upgradebility vs the x86-64 platform that still allows you to repair / upgrade RAM, memory, CPU's and other parts in an affordable manner.

- And because of the above two, all M1 devices with low ram and storage, have planned obsolescence of 3-5 years built-in, along with a kill switch to totally disable the device.

Apple has a found a great fit for their business model with the ARM SoCs. Even when (not if, when) AMD and Intel bring out better processors, Apple will stick with their ARM SoCs because todays computing power has far outpaced the demand made by the common softwares used by all. And Apple can cater to the common denominators with their own OS + CPU + 8GB + 256 GB NvME quite well for maybe another decade.

I am happy there is some good tech development and competition in computer systems. But my Intel Mac Mini will be the last mac I will buy from Apple. macOS Mojave still runs fine on it. Otherwise there's always Windows, Linux and FreeBSD. That's the real advantage of the x86-64 platform that people like me will never sacrifice for closed systems like the M1 devices.

Have you opened many x86 devices of a similar form factor to the current M1 devices? I haven’t seen a socketed CPU in a laptop in over a decade, and the vast majority of ultrabooks and thin-and-lights have soldered RAM now too. The latest trend has been to start soldering SSDs as well.

can you elaborate?

But if a government (or Apple) wants, this can be abused - for example, tomorrow if your country goes to war to the US, the US government could ask Apple to disable all Apple devices in that country, and Apple could do it, whether you like it or not.

(The conspiracy theory part that others are hinting at is that many believe that this can be easily extended to totally cripple the device and make it unusable.)

I didn't insinuate anything like that. I was just pointing out that it exists.