3 ms·
when the m1 initially shipped, i was watching this issue like a hawk. rosetta was really cool technology, but they seemed to really miss the mark in terms of ma
by a-dub 4y ago
when the m1 initially shipped, i was watching this issue like a hawk. rosetta was really cool technology, but they seemed to really miss the mark in terms of many developer workflows that involve intel vms and containers.
it was particularly interesting to me as i always got the sense that a lot of the success of the intel era macs was carried by their popularity and (and recommendability) amongst the internet development and engineering crowd. it seemed to me like a mistake to potentially alienate that group.
- MBCook 4y agoI figured it was largely a time management thing. They could only do so much (I mean they moved the whole base OS architecture… again). Glad to see it. Hope that by the time I get my next work laptop it’s still there, or better yet we’ve moved to a newer version of the software where this isn’t a problem.
- dilyevsky 4y agoIme podman (or docker) + qemu-user-static covers nearly everything. There are some issues with older go binaries emulation but most of c/c++ x86 code works as is
- a-dub 4y agowhat's the performance cost vs. intel code on the host under rosetta2 and native arm code on the host?
- dilyevsky 4y agoI think it depends greatly on what instructions are being used (sse, avx, etc vs neon). Some benches I’ve seen boast rosetta2 is only 30% hit but that’s doubtful to me based on my own experience running factorio =)
- deleted 4y ago[deleted]