I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…
Ask HN: How are you dealing with the M1/ARM migration?
111–120 of 284 posts
Re: Ask HN: How are you dealing with the M1/ARM migration?
#112I’m working on re-factoring a developer environment from using vagrant/virtualbox and docker to only docker. The prior goal was to mock production as closely as possible. The realization is that macos as a host machine for orchestration is close enough to build. More strict validation can be done in CI and a staging env. So for this project, the forced transition away from virtualbox Has actually led to simplificatio…
Re: Ask HN: How are you dealing with the M1/ARM migration?
#113Re: Ask HN: How are you dealing with the M1/ARM migration?
#114Re: Ask HN: How are you dealing with the M1/ARM migration?
#115I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…
E.g. if I wanted to start building ARM binaries on a x86 host, is that the sort of thing this would enable?
Re: Ask HN: How are you dealing with the M1/ARM migration?
#116Everything was far easier than I expected it to be, the only issues I had was with installing python (a few cli Utils required it) but everything else has been smooth sailing and a much better experience than running things on my 2019 MBP
I’m not a huge docker user, but I run it for a few things and again, it was all smooth sailing.
Re: Ask HN: How are you dealing with the M1/ARM migration?
#117Oracle sucks. I mean in general, but they have also not released ARM instantclient or even an ARM version of Java. I think its crazy that I'm using Microsoft's version of ARM java. I'm also using Windows 11 ARM in Parallels, which does seamless emulation of Oracle instantclient / Java / PL/SQL Developer. So most of my workflow has not been interrupted. Still, just another excuse to move to a better database. Now all…
Java has been available on ARM since the days of Nokia phone dominance. Not sure what you're referring to?
Re: Ask HN: How are you dealing with the M1/ARM migration?
#118Re: Ask HN: How are you dealing with the M1/ARM migration?
#119Earlier quoted context omitted.
> highly performant Last thing I read, 70% of the native performance was shown by running GeekBench through Rosetta (with a few odd results noted). If somebody has better info... Edit: I see that Nov 2020 checks returned an 80% performance, and there was discussion on HN at (at least) https://news.ycombinator.com/item?id=25105597
Here are my numbers for the original M1 (not Pro or Max) soon after release: ARM Geekbench single core on M1 MacOS is 1734. ARM Geekbench single core on WinARM in VM on M1 is 1550. x86 single core on i9 MB Pro MacOS is 1138. x86 in emulation on M1 MacOS is 1254. Yes, 72% x86 Rosetta vs. M1 Native. However, x86 Rosetta on M1 was faster than the previous i9 2019 Macbook Pro x86 native. I consider that to be performant…
Re: Ask HN: How are you dealing with the M1/ARM migration?
#120For now I'm ignoring it, I'm usually about two to three years behind the curve and by then the bugs have typically been ironed out. I won't be running macOS anyway, but will wait until a fully supported version of Debian is out there that uses all of the peripherals properly. They call it the bleeding edge for a reason and I see no reason to spend extra effort that isn't driven by an immediate need. I like tech, I ca…
You will be waiting far more than 3 years.