I am currently (literally waiting on a EC2 Image Builder pipeline to complete as I write this) rewriting our dev VM to work on EC2 rather than VirtualBox on our

I am currently (literally waiting on a EC2 Image Builder pipeline to complete as I write this) rewriting our dev VM to work on EC2 rather than VirtualBox on our MacBooks. I'm doing this for two big reasons: One, the VM won't run well on future Macs. We're using Intel MacBooks on Big Sur because there's a bad interaction between Monterey and the VirtualBox kext that I can't figure out; and because making our VMs work across Intel and ARM would require a rewrite. Second, and more importantly, debugging why the VM isn't working on someone's laptop is a massive pain. My goal in moving the VM to the cloud is to reduce the surface of things that I have to troubleshoot. If ssh works on your laptop then (the hope is) I don't need to mess with your laptop any more. If the VM breaks, then when I fix it it'll be fixed for everyone at once. Believe me, that's not the case with the local dev VM despite the entire thing being scripts in a git repo. I'm trying my best to keep the new dev experience as painless as possible, but at the same time, moving the VM to work in a consistent and stable environment also improves the dev experience along with my operational experience. It'd be fantastic if we could run everything locally and nothing ever broke and everything that worked on my machine worked on prod too, but that's simply not the case