News for hackers. Stuff that matters.
Re:Apple's M4 Max chip is the fastest single-core performer ... by jihadjihad on Friday November 01, 2024 @10:56AM (#42017522)
I've got a coworker who still has an Intel MacBook Pro, 8-core i9 and all that, and I've been on M chips since they launched. The other day he was building some Docker images while we were screensharing and I was dumbfounded at how long it took. I don't think I can even remember a recent time when building images, even ones pushed to CDK etc., takes more than a minute or so. We waited and waited and finally after 8 minutes it was done.

He told me his fans were going crazy and his entire desk was hot after that. Apple silicon is just a game changer.

Re:Apple's M4 Max chip is the fastest single-core performer ... by grahamj on Friday November 01, 2024 @05:10PM (#42021591)
For sure. I had one of those for work when I got my personal M1 Air and I couldn't believe how much faster it was. A fanless ultraportable faster than an 8-core i9!

I was so happy when I finally got an M1 MBP for work because as you say Docker is so much faster on it. I feel like I don't wait for anything anymore. Can't even imagine these new chips.

Re:Apple's M4 Max chip is the fastest single-core performer ... by MBCook on Friday November 01, 2024 @11:36PM (#42023885)
Same situation for me.

I’m going to be very happy when it’s time to replace my Intel MBP at work.

It’s rarely loud, but boy it likes to be warm/toasty at the stupidest things.

Re:Apple's M4 Max chip is the fastest single-core performer ... by rahkiin on Friday November 01, 2024 @06:52PM (#42022346)
Oh I know the feeling… when using ict-managed windows laptops at work
Re:Apple's M4 Max chip is the fastest single-core performer ... by moondev on Friday November 01, 2024 @07:02PM (#42022399)
Sounds like they were building an aarch64 image, building an x86_64 image on Apple Silicon will also be slow - unless you are saying the M* builds x86_64 faster than an i9?
Re:Apple's M4 Max chip is the fastest single-core performer ... by robotresearcher on Friday November 01, 2024 @07:35PM (#42022650)
Are you saying it's faster to build a binary with native architecture? Why is that?
Re:Apple's M4 Max chip is the fastest single-core performer ... by 0x457 on Friday November 01, 2024 @07:57PM (#42022800)
Because there two ways to get to the same result:

- use native toolchain to produce artifacts for a different architecture

- use emulation to run different arch toolchain to produce different arch artifacts

First one is fast, second one is slow. In docker only second variant is possible.

Re:Apple's M4 Max chip is the fastest single-core performer ... by PoignardAzur on Saturday November 02, 2024 @05:47AM (#42025222)
That doesn't sound right. It's not like you need to run in WebAssembly to produce WebAssembly binary.

Why would you need to emulate x86 to produce x86-shaped bytes?

Re:Apple's M4 Max chip is the fastest single-core performer ... by kapoolo on Saturday November 02, 2024 @06:53AM (#42025525)
Emulating the target architecture's SDK can be much easier and simpler to setup and avoid mistakes. You do not need to make any changes or configuration to make it compile.

For exmaple, that is generally the way you cross compile Flatpaks in cli or ide. In, for example, GNOME Builder you can just select the device you want to build for, like your smartphone, and it uses QEMU to emulate the entire SDK in the target architecture, you can also seemlessly run the Flatpak on your host through QEMU user mode emulation too.

Re:Apple's M4 Max chip is the fastest single-core performer ... by 0x457 on Saturday November 02, 2024 @01:18PM (#42027705)
Well, WASM runs in a VM, not on a hardware? There isn't hardware that runs WASM directly (at least nothing serious, maybe some hobby FPGA or POC).

So when you compiled to WASM you're going with route #1. WASM was designed with this this in mind.

Re:Apple's M4 Max chip is the fastest single-core performer ... by robotresearcher on Saturday November 02, 2024 @05:47PM (#42029439)
A compiler doesn’t need to run the instructions it generates. Why should cross-compilation be slower than native compilation?
Re:Apple's M4 Max chip is the fastest single-core performer ... by 0x457 on Saturday November 02, 2024 @07:40PM (#42030044)
It doesn't need (unless it does in some cases), but entire build process needs to be aware of what needs to be native and what doesn't. Mainly a lot of issue would come from linker. Yes, it's not part of the compilation technically, but aside from hellworld.c everything you build would probably require linker at one point or another.

Then there are some gcc quirks:

- for gcc compilation target is defined when gcc is compiled, so only way to cross-compile with gcc that I know of is emulation of target arch and runing gcc for target arch

However, we're talking about docker containers here, emulation would be the default way and path of least resistance.

Again, I will reiterate: every cross-compilation strategy falls into one of these two buckets. In some cases what I've describe in #1 is possible (WASM, java bytecode or really (almost) anything that targets a VM), in some cases it isn't and then you gotta go with #2 (docker, gcc)

Re:Apple's M4 Max chip is the fastest single-core performer ... by robotresearcher on Saturday November 02, 2024 @09:15PM (#42030500)
How about Xcode's LLVM on an Intel Mac building for ARM iOS?
Re:Apple's M4 Max chip is the fastest single-core performer ... by 0x457 on Sunday November 03, 2024 @01:46PM (#42035151)
Two things here:

- clang and LLVM don't have that GCC quirk (LLVM support less platforms, so give gcc some credit)

- it was in apple's financial interest make sure their things are easy to cross-compile.

- linker job is extremely straighforward in case of iOS

   - everything is provided by either apple or application developer
Re:Apple's M4 Max chip is the fastest single-core performer ... by JohnBooty on Saturday November 02, 2024 @01:01AM (#42024171)
That was what finally got me to spend the cash and go with Apple Silicon - we switched to a Docker workflow and it was just doooooog slow on the Intel Macs.

But this M1 Max MBP is just insane. I'm nearly 50 and it's the best machine I've ever owned; nothing is even close.