Go: What We Got Right, What We Got Wrong

Re:Go: What We Got Right, What We Got Wrong by iainmerrick on Friday January 05, 2024 @03:30AM (#38876963)

That term isn’t meant to include mobile apps, desktop apps, web apps (even though those all use the internet, of course). Nobody is using Go for any of those, as far as I know.

So I think it is a useful term, and captures the things Go is good at surprisingly well.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by bb88 on Friday January 05, 2024 @02:55PM (#38883960)

I actually kinda thought that Google should have made Go the default language for android. It could have been a compelling argument to the rest of the world as a reason to use it as a systems language.

It's feels like they didn't want to dog food it outside of their servers, though.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by iainmerrick on Saturday January 06, 2024 @05:52AM (#38890342)

Android was already using Java and Dalvik (their JVM variant) at that point, so switching to Go would have been a massive undertaking.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by thegeekpirate on Sunday January 07, 2024 @11:41AM (#38902628)

> Nobody is using Go for any of those, as far as I know.

Quite a few of us are, fwiw. I personally have done all three, Tailscale uses Gio UI for their mobile apps, and a fair amount of games have used https://ebitengine.org to release for Xbox/Nintendo Switch/Mobile/Webassembly/Cross-platform PC.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by iainmerrick on Sunday January 07, 2024 @06:48PM (#38906452)

I hadn't heard of either of those projects -- both look really cool. Thanks for the pointers!

[ Parent | on HN ]