Funny to see this on the front page the same morning that I switched back to using a remote dev box.
Lima constantly has i/o issues (usually network hangs, local connections within the VM). It's pretty rough to use when I need to do docker in Lima.
Lima constantly has i/o issues (usually network hangs, local connections within the VM). It's pretty rough to use when I need to do docker in Lima.
I really like being able to read some tech on my iPad, see something I want to try, and 5 seconds later I am SSHed/Mosh'ed into my remote dev VPS.
EDIT: that said, I do have Lima installed on my M1 MacBook Pro.
On the other hand, it has much much less CPU than an MBP, and usually no GPU at all.
On the third hand, the cloud allows one to quickly start more VMs, and to shut them down as quickly, something that's possible but a bit more limited on a laptop / desktop.
Pay for 3 years of AWS savings plans to make it cheap. Perhaps run a permanent instance for small things, make a setup that lets me spin up super power machines when i actually want to build.
Most of the time I'm at my ipad remoting in Im not actually compiling, just editing. I can just edit locally and pay for the few seconds/minutes it takes to build..
because honestly after about 3 years i always want to upgrade
and i can get windows that are completely functional for me on remote monitors with ipad now. just starting to wonder why im paying for physical compute power but 99% of the time browsing the web and editing code but not building it.
I do a ton of work on my iPad Pro: writing, research, using Google Colab for model development, and my beefy VPS remote dev box.
All that said, having good Linux and MacBook Pro laptops with a really large external monitor is sometimes very effective.
Depends on what I am working on.