I started doing all my development inside a virtual machine. UTM on the M1 chip running Ubuntu ARM works very well and has minimal impact on battery life. The VS Code remote extension makes development inside the VM feel like its local.
What I dislike in the VM approach is that the development machine and the host are somewhat disconnected and it's non-trivial for them to share files. Also, I'm concerned I'll write software with too many linuxisms that would render it incompatible with other Unixes (which are still used in far too many places). With my tooling, I even try hard to make it work on Windows, just in case.
That's why I use Parallels Desktop, even though I would prefer to use open source software. They provide great file system integration on common OS plus a few other things like GPU graphics (I tried with windows 10 arm).
So you run a Linux box using Parallels and use VS Code or something on the Mac side to edit files? I'm interested in adopting a similar workflow, so your guidance would be appreciated.
You may want to look into Vagrant. It automates the setup of the VMs (and the sharing of files between them) so you can quickly test between say Ubuntu and FreeBSD.
I wonder if they tried to create something better than Random Access Memories for the last 7 years only to find out that it’s the best to leave it at that high note.
I am in the same boat. I love this Laptop, but Lightroom (CC) is really slow compared to how it runs on iOS. I would assume the new M1-based machines could run the iOS version of Lightroom almost out of the box.
I find that well-executed strength training (i.e. with proper form) eliminates all kinds of back-related issues for me. This talk has been really eye opening for me:
+1 on this, for me deadlifting has single-handedly fixed my back. I tried PT for it, with mixed results, but once I started lifting it completely went away. YMMV, but it's worth considering for sure.
I'm clearly doing something wrong, but lifting has driven every time I've injured my back in the past 5 years. I've had trainers coach me on form, and _most_ of the time I'm fine. But if I have bad form p% of the time (e.g. 0.5-3%), and working out becomes a ~daily thing, then I have a handful of opportunities per year to injure myself.
You kind of provide recipe how to avoid it yourself. One suggestion that might or might not be relevant - don't do weightlifting at your proper max, and don't push your limits that way. Its a way to grow fast but also sure way to injury. There is no way to be at your limit and keep the proper perfect form, every time. You can always add more repetitions to workout.
For me weightlifting is about staying in shape for things like mountain adventures, feeling great, looking good. But Arnold-look is a silly goal for long term wellness, and so are the methods to get there. Once I stopped pushing the numbers and focused on more repetitions, I never had any injury. That's worth much more than some momentary number of kilos/pounds you did today - nobody will care about that tomorrow, but injuries remain, sometimes forever.
YMMV, but I found the following articles quite useful to 1) help self-manage symptoms brought on during strength training, and 2) to stop obsessing about my using "bad" form during training:
I use Pinboard in combination with a Raspberry Pi (running Calibre + Mozilla Readability) as my Read Later service. Once per day the Raspberry Pi fetches unread bookmarks from Pinboard and compiles an eBook that is then sent wirelessly to my Kindle. This has replaced Instapaper/Pocket for me. Thanks to Mozilla Readability the text/image extraction works in most cases better than other Read Later services + I like having all my bookmarks in one place (and one service less to pay money for!). I've written a blog post about it and open-sourced all my work: https://christianhans.info/12791/running-your-own-read-later...
