I did go through the Go tutorial many many years ago, but it's been so long I don't remember anything. I do remember it was an enjoyable process though, and I'd love to pick it up again.
This post resonates. I recently built a little web service to scratch an itch I've been having and after discussing the options with Claude we settled on Go, and honestly it's been fantastic. Highly performant, native threading, dead simple to deploy with containers. And I don't even know how to read or write Go.
This is a very silly restriction, at least to apply uniformly to all Macs. I think if you buy a more powerful Mac they should let you virtualize more Mac instances. Like an M5 maybe limit to 2, but maybe let an M5 Pro do 4 and an M5 Max do 8 or something.
I'm neither apparently, which I guess is a relief? Some of the questions I felt didn't have an answer I would select, like the inner monologue one. I generally don't have an inner monologue as I understand it described by people who do. Also, there's way more wrong with the world than those four answers.
I feel like Apple wouldn't want to make full Linux work on their hardware, but they could enable their Darwin kernel to emulate Linux syscalls and provide a way to boot into a mode that basically loads the kernel and whatever Linux shell you want
I'm going to echo what others have said, Xcode will run on 8GB but the moment you need simulators or iOS canvas previews it will need more memory. You can probably get by on the Neo, but it won't be ideal. I suggest an M4 Mac mini instead.
Huge win on the name change. I'm never going to install an app called Pingstalker on my computer, it would feel gross and I'd worry other people might see it and be alarmed by it.