Live data from Hacker News

14-inch MacBook Pro review: A Mac Pro in your backpack

sixcolors.com

11–20 of 244 posts

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#11
post #5

Earlier quoted context omitted.

Of course. Any time you try to run a non-ARM binary on an ARM CPU without some form of translation or emulation, it will fail. This is also true for any other CPU architecture. If you want to know about specific compatibility issues, I'm happy to try to help as I've been using an M1 Air as my daily driver for many months now.

Did they finally get Docker working on the M1 chips?

Yes. https://docs.docker.com/desktop/mac/apple-silicon/

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#12

Do ARM compatibility issues still exist?

Yes, but it's very rare now a days. I live in JVM land and there are quite a few native JNA libraries that I have run into issues with. One example is vlcj [1] I just ran into yesterday. I have yet to dig deeply into the issue just yet, but it's giving me the fun "no compatible architecture found error". SWT and JavaFX both fully works with arm now though, so I am pretty happy on that front. GraalVM native-image also does not support building ARM on Mac yet either. On the C/C++ side of things I have not ran into any incompatibility issues in the last 5 months. I'd say 99% of my time is smooth sailing at this point.

[1] https://github.com/caprica/vlcj

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#13

Earlier quoted context omitted.

Of course. Any time you try to run a non-ARM binary on an ARM CPU without some form of translation or emulation, it will fail. This is also true for any other CPU architecture. If you want to know about specific compatibility issues, I'm happy to try to help as I've been using an M1 Air as my daily driver for many months now.

> without some form of translation or emulation IIRC that's why Rosetta2 exists. The question is more whether there are issues despite that

I don't think I've ever had an issue related to Rosetta2. Everything I had to run on it worked flawlessly and without any noticeable performance hit.

This is only my own anecdote though.

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#15

Do ARM compatibility issues still exist?

I haven't run into any issues. Homebrew seems to be (mostly) working, and most vendors have created universal images at this point. I think the only thing I'm personally waiting on is VMware Fusion (currently in beta).

Swift still doesn't have an Arm docker image from the official Swift.org group.

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#16

Earlier quoted context omitted.

> without some form of translation or emulation IIRC that's why Rosetta2 exists. The question is more whether there are issues despite that

I don't think I've ever had an issue related to Rosetta2. Everything I had to run on it worked flawlessly and without any noticeable performance hit. This is only my own anecdote though.

There have been some font rendering issues in Ultimaker Cura (which is written in Python) that ran as x86 on M1. These have been resolved in the Python library.

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#18
post #6

Do ARM compatibility issues still exist?

I mean, yeah. You're not going to be running anything 32-bit, and you can't use OpenGL or Vulkan, which already rules out a decent handful of workflows (including but not limited to my own). On top of that, there's legendary Docker issues that plague pretty much anything running MacOS, and there still isn't a competitive, complete package manager. eGPUs are almost completely off the table, and if they do work you won…

OpenGL still works on the M1 (Apple designed their own GL-over-Metal driver), albeit with the OpenGL version limitations from modern macOS in general. Vulkan works over MoltenVK.

Other than old games, I'm not sure why 64-bit only is an issue.

I've not hit any Docker-on-macOS issues with what I've used it for, at least.

Re: 14-inch MacBook Pro review: A Mac Pro in your backpack

#19
post #16

Earlier quoted context omitted.

I don't think I've ever had an issue related to Rosetta2. Everything I had to run on it worked flawlessly and without any noticeable performance hit. This is only my own anecdote though.

There have been some font rendering issues in Ultimaker Cura (which is written in Python) that ran as x86 on M1. These have been resolved in the Python library.

In fairness, I've seen font rendering in Cura on Linux as well.
Post reply on HN