4 comments

[ 3.5 ms ] story [ 27.6 ms ] thread
I recently tried to get Go running on a Windows PC and was surprised at how immature the ecosystem is for that configuration. The thing that seemingly everyone uses for hotreloading (Air) can't be configured to support Windows and Linux at the same time. Console output from the application in question was also completely missing, which admittedly, they fixed as soon as I created a bug report and repro project.

I want to use Go for some low-cost projects hosted on VPS's but the dev experience isn't quite there yet.

I'm actually more excited about 1.26 mainly because of the streamlining of a lot of out-of-my-control systems. I love that I can new() an expression.
> But together, they address problems teams hit at scale:

> [...] Too much boilerplate around pointer values

The "author" leaned a little too hard into the LinkedIn voice. This improvement has nothing to do with the scale of your team or your workload.

Do yourself a favour and just read https://go.dev/doc/go1.26