Earlier quoted context omitted.
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?
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.
Apple's M4 Max chip is the fastest single-core performer in consumer computing
521–530 of 551 posts
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#522Earlier quoted context omitted.
They claimed that it wasn't covered because the machine was brought in Germany. I live in The Netherlands and brought it here. Also I contacted Apple Support to checked my serial number and then gave me the address to take it to. Which I did. They charged me $100 to get my machine back without repair. Also bear in mind that the EU is a single market, warranties etc are, by law, required to be honoured over the ENTIRE…
So you haven't purchased it from Apple but instead you've purchased it from Amazon. This may change things. In Europe you have two ways of dealing with it, either by manufacturer warranty (completely good will and on terms set by the manufacturer) or by consumer rights (warranted you by law, overruling any warranty restrictions). Sellers often will try to steer you to use warranty as it removes their responsibility,…
I'll keep buying from Amazon as their support is great and prices competitive. I don't trust Apple buying from them directly.
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#523Earlier quoted context omitted.
In that case, you can get the mini with 64GB of memory for $1999.
It would be $2,199 for the highest end CPU and the 64GB of memory but I think you're point remains: the Studio is not a great buy until it receives the M4 upgrades.
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#524Earlier quoted context omitted.
It's my plex server and nas (m1). I've abandoned all the complicated complications and just have an 8 bay thunderbolt enclosure full of drives (JBOD) And pg server. And a few web sites server. And something running in orb stack. It's the 8gb model and I have around 2gb free most of the time
What enclosure do you have? Do you like it?
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#525Earlier quoted context omitted.
Geekbench is run pre-release by the manufacturers.
But by definition that means it’s not a production machine yet. So it doesn’t invalidate Apple‘s chip being the fastest in single core for a production machine.
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#526Earlier quoted context omitted.
Did no one check the scores? They're not the top consumer CPU by quite a range. It's probably the best power per watt, but not the most powerful CPU.
The performance-per-watt isn’t necessarily the best. These scores are achieved when boosted and allowed to draw significantly more power. Apple CPUs may seem efficient because, most of the time, computers don’t require peak performance. Modern ARM microarchitectures have been optimized for standby and light usage, largely due to their extensive use in mobile devices. Some of MediaTek and Qualcomm's CPUs can offer bet…
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#527Earlier quoted context omitted.
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.
A compiler doesn’t need to run the instructions it generates. Why should cross-compilation be slower than native compilation?
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 in consumer computing
#528Earlier quoted context omitted.
I blame it on the PC crowd being unconsciously salty the most prestigious CPU is not available to them. You heard the same stuff when talking about Android performance versus iPhone. There is a lot to criticize about Apple's silicon design, but they are leading the CPU market in terms of mindshare and attention. All the other chipmakers all feel like they're just trying to follow Apple's lead. It's wild.
I was surprised and disappointed to see that the industry didn’t start prioritizing heat output more after the M1 generation came out. That was absolutely my favorite thing about it, it made my laptop silent and cool. But anyway, what is it you see to criticize about Apple‘s Apple Silicon design? The way RAM is locked on package so it’s not upgradable, or something else? I’m kind of surprised, I don’t hear a lot of p…
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#529Earlier quoted context omitted.
That's okay, Factorio has awesome Apple Silicon support.
What about Paradox games? genuinely curious about that.
That's the thing with macs, all the strategy games tend to release there because the market for mac users and strategy gamers is a circle.
Re: Apple's M4 Max chip is the fastest single-core performer in consumer computing
#530Earlier quoted context omitted.
A compiler doesn’t need to run the instructions it generates. Why should cross-compilation be slower than native compilation?
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…