Orbstack I thought https://orbstack.dev/ is what people are using these days instead of UTM. Am I mistaken?
Maybe it's still getting out there? First time seeing it, looks super promising. Thanks for sharing :)
Ode to the M1
11–20 of 286 posts
Re: Ode to the M1
#12I like UTM too. I must be doing something wrong though. I created both X86 Ubuntu and Debian 10 VMs. They are usable, but not quick. I have been blown away how fast Rosetta 2 x86 programs run my m1. The arm embedded gcc too chain compile code 4x faster than the native x86 MBPro from a year or so ago. But the UTM VMs run about 3x slower.
You can't run x86 Linux quickly on macOS. What you can do is to run ARM Linux quickly on macOS and run x86 programs inside of that Linux with Rosetta quickly.
Re: Ode to the M1
#132020 M1 Air here, still running strong and will soon hit 3 years (bought the day it launched).
So strong that despite finding the 15 inch air appealing just in terms of screen real estate, this current laptop doesn't feel dated. Especially since work provided me with an intel macbook pro with great spec but .. just doesn't compare with the exception of remote monitor count.
Re: Ode to the M1
#14Orbstack I thought https://orbstack.dev/ is what people are using these days instead of UTM. Am I mistaken?
Orbstack does not seem to run Windows.
Re: Ode to the M1
#15Orbstack I thought https://orbstack.dev/ is what people are using these days instead of UTM. Am I mistaken?
I only use utm to run chrome for testing because when run natively with selenium it steals the window focus all the time. I want the test to run while I'm coding and also see and interact with it.
Re: Ode to the M1
#162020 M1 Air here, still running strong and will soon hit 3 years (bought the day it launched). So strong that despite finding the 15 inch air appealing just in terms of screen real estate, this current laptop doesn't feel dated. Especially since work provided me with an intel macbook pro with great spec but .. just doesn't compare with the exception of remote monitor count.
We got it the same day! I coded >100k LoC (the whole core of the OKcontract codebase) solely on that machine, without any external screen.
Working flawlessly since day 1.
Re: Ode to the M1
#17> Software "engineers"
> For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it.
Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damaging this is?
I hope Electron/CEF die soon, and people get back to building applications that don't consume hundreds of megabytes of RAM to render a hello world.
Re: Ode to the M1
#18UTM is great, but sort of useless for many of my most acute Windows needs: talking to some random peripheral or device that only has a closed-source x86 windows driver.
Re: Ode to the M1
#19I like UTM too. I must be doing something wrong though. I created both X86 Ubuntu and Debian 10 VMs. They are usable, but not quick. I have been blown away how fast Rosetta 2 x86 programs run my m1. The arm embedded gcc too chain compile code 4x faster than the native x86 MBPro from a year or so ago. But the UTM VMs run about 3x slower.
You can't run x86 Linux quickly on macOS. What you can do is to run ARM Linux quickly on macOS and run x86 programs inside of that Linux with Rosetta quickly.
Wait you can use Rosetta inside a Linux VM?
Re: Ode to the M1
#20> Software "engineers" > For every extra cycle an hardware engineer can squeeze out of silicon, you will find a programmer adding one hundred cycles to their program[6]. In other terms, I fear that once devs figure out how powerful the M1 is, they will throw more "features" at it. Can we please stop replicating the "growth" fallacy into software ecosystems? Haven't we learnt enough about how unsustainable and damagin…
>I hope Electron/CEF die soon, and people get back to building applications that don't consume hundreds of megabytes of RAM to render a hello world.
Yes, so we can go back to writing a hundred lines of imperative code to render hello world.