this post was submitted on 11 Mar 2024
192 points (94.9% liked)

Technology

59206 readers
2539 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Interesting. Samsung making a bold move here, but one that could make sense.

you are viewing a single comment's thread
view the rest of the comments
[–] Spiralvortexisalie@lemmy.world 12 points 8 months ago (1 children)

I have been running Windows 10+11 on arm for years now, the next version of Windows Server 2025 already has an arm preview release. Windows ARM has for a long time had x86 emulation, and has supported x64 emulation since about the start of COVID.

[–] abhibeckert@lemmy.world 3 points 8 months ago* (last edited 8 months ago) (1 children)

Is it actually emulation? Macs don't do that.

They convert the x86 code into native ARM code, then execute it. Recompiling the software takes a moment, and some CPU instructions don't have a good equivalent, but for the most part it works very well.

[–] Spiralvortexisalie@lemmy.world 4 points 8 months ago (1 children)

MacOS does use the term translations for its Rosetta Layer while Windows Arm uses the term emulation. I do believe the technical difference is that MacOS converts x64 code to arm64 on the fly, while part of the reason for emulation on Windows is to support x86 and other architectures. Someone more knowledgeable than me may be able to better compare the two offerings.

[–] BorgDrone@lemmy.one 6 points 8 months ago

macOS converts x86 code to ARM ahead of launching an app, and then caches the translation. It adds a tiny delay to the first time you launch an x86 app on ARM. It also does on-the-fly translation if needed, for applications that do code generation at runtime (such as scripting languages with JIT compilers).

The biggest difference is that Apple has added support for an x86-like strong memory model to their ARM chips. ARM has a weak memory model. Translating code written for a strong memory model to run on a CPU with a weak memory model absolutely kills performance (see my other comment above for details).