So I've been devving in Go for about 11 years full-time and prefer it for pretty much everything. The main thing though, is that I reach for Go because I know I'll need it *later*. For example, before my gopher awakening I was a Ruby on Rails dev (4.2). The productivity was incredible, and I was slamming out CRUD apps and stuff basically instantly. I could write some yaml, put files in the right place and it'll magically create a CRUD app, with free auth, admin panel, console for debugging, ORM etc. But as soon as you wanted to do something novel, or even just something really specific, then it suddenly gets really hard. But you don't **know** that you need it until you do, and then its too late. For example, a client might want you to tie into an Ethereum node to index NFT transfers. Maybe LLM inference? Or asynchronous jobs. PDF OCR? S3 mirroring. Kubernetes pod stats. Traces or spans. Maybe you have to send a single binary or cross compile into an ARM target. The point is Go is capable is stuff you're not aware that the product requires yet, and that's where it shines because there's no magic and its low level. Secondly, I just hate reading prose in my documentation. Markdown for docs suck so bad. Godoc is amazing. You probably know all this already, but I hope that explains my thinking.