Prolonged compiling tasks will thermally throttle the 1185g7 chip long before the M1.

It will run circles around the 1185g7 compiling large codebases.

Passmarks across hundreds of benches show a 25% single and 40% multithreaded performance boost over the 1185g7.

I’ve got an i9 8/16 laptop chip and the 13” M1 is trading blows with my laptop despite 2-3x the thermal headroom and considerably less cores/threads across all workloads.

The frame.work people are very explicit that they’ve designed the cooling system to permit you to run the CPU fairly hard. It can dump 28W continuously according to https://frame.work/gb/en/blog/the-upgradeable-mainboard.

The i9 Apple laptops were notorious for not having a cooling system that could match the heat output of the CPU & throttling almost instantly.

Modern Intel laptop CPUs are no where near the performance / W of the M1, but they are considerably better than those that Apple stuffed into their laptops a few years ago with inadequate cooling I believe.

That was a firmware issue pre 2019 model that was corrected in a few weeks that got overblown. The throttling problem doesn’t exist anymore.

The only problem with the first generation framework laptop is intel’s quad core CPU because of thermal and power problems associated with their process nodes.

Hex core is really the lowest I will go now for anything over $1000. If this was a Ryzen 5800u, I’d have bought one already.

On my 1185g7 laptop, the browser benchmark Speedometer 2.0 scores 116. On my M1, I get 288. That's a bit more than "slightly ahead". The M1 absolutely smokes Tiger Lake and even Tiger Lake-H.

Sure, but that's expected because ARM essentially has hardware JavaScript acceleration built-in via FJCVTZS[0]. I personally don't find JavaScript specific benchmarks to be a good indicator of general computing power. (Ultimately, I spend little time in a web browser.)

FWIW, Cinebench multi-core benchmark is around 20% faster for me on the M1.

[0]: https://developer.arm.com/documentation/100076/0100/a64-inst...

> I personally don't find JavaScript specific benchmarks to be a good indicator of general computing power.

Many of us spend substantial periods of time writing up the technical documentation in Confluence or use JIRA. Confluence alone loads approximately 22Mb of mangled and compacted JavaScript for each open page in a separate browser tab.

Before M1, Confluence and JIRA were the single most source of a sustained battery drain, irrespective of the browser. On M1 based laptops, the battery impact is so negligible that it can be considered non-existent. How much of this subjected experience can be attributed just to the the ARM 8.3 JavaScript hardware acceleration is an interesting question as the JavaScript browser performance on Intel CPU's has also been affected by Spectre and Meltdown mitigations in the CPU microcode.

I doubt that instruction is relevant. It comes down to an abundance of microarchitectural resources on the M1. A 12th-gen Intel CPU gets 310 on this benchmark while having no particular accelerators. They just added tons of caches and buffers, like the M1 has.