I've used one, not great, but why would you spec a Go out, its a cheap coffee shop laptop, and at least warranty is pretty good in Asia. Keyboard broke, okay do you have a CC, yep, well send you a new one, send us the old back, as long as it isn't your damage (i guess water or obvious drop) its job done and no charge to CC. Small delay as part had to come from Hong Kong to Thailand first. Much better than travelling to and speaking to bloody genius if you happen to get an on the spot appointment with one of the clowns.
This was meant in response to the people complaining about build quality
> I've used one, not great, why would you spec a Go out, its a cheap coffee shop laptop
I've done most of my recent coding work on a Go, like, most of my sixel stuff!
The size is just right, so it followed me everywhere, and by spending 5 min on it here and there, I could get a lot of work done!
Also LTE is great: I don't want to waste even a minute looking for Wifi password. That's another productivity multiplier!
After that, I got a X1 nano, it's a great device but a bit too big for me, even it's just about 1 inch larger in both dimensions and about the same thickness.
More recently, I've moved to a X1 Fold, and it's even smaller than a Go when folded so it's now my favorite device! There were a few drivers problems I had to tackle, but now it's rock solid on Windows 11. Also, the OLED screen is ideal to use at night!
>you can easily find 100 developers with years of React experience
And nearly all of them completely useless. Most react devs don't even understand Fibers or have any empathy with DOM, javascript, and other parts of the common web stack, most can barely explain when something will render, what memoization is, what reference equality is and so on. It's easy to breach the 10x factor as React dev and 100x is achievable.
Slightly OT, How do you do "re-authenticate before connecting" (https://tailscale.com/kb/1193/tailscale-ssh/) when using Google identity, we are using Google Oauth2 and latest identity SDK but can't see how to force a user to re-authenticate if logged in, do you just make a random unique claim?
This was meant in response to the people complaining about build quality