In reverse order:

• Directly mapping structs to JSON is a solved problem in userland for every major language
• yes it does, and worse it’s part of the return signature and null is super-prevalent of necessity as a result
• even java doesn’t do that any more, but fine I guess
• cool, but access modifiers actually make a lot of sense. Go’s solution to this is to use capitalisation as a marker, which has no ‘inferential readability’ – public/private is obvious. Foo/foo? Considerably less so

Further, meta programming in go sucks donkey balls. Sure, it finally got generics but also they suck. Last I checked it still didn’t even support covariance.

Dude, weird ass-comment. I can share my opinions and they don’t have to be positive ones. Go is a tool and its purpose is to be an aesthetic stain on the realm of software.

Thank you for your attention

That’s completely fair, thank you for your service

Ironically Go is such a shite verbose language that basically everyone I know who has to work with it will use an llm code-assistant tool to avoid having to write all the boilerplate themselves.

I know of no other language that comes close to prompting the level of LLM-dependency that Go inspires.

Edit: well, seems like this goes against the popular consensus but I stand by my guns if the down votes are from average Go enjoyers. If, on the other hand, the down votes stem from the sentiment that even Go should not be vibe coded, I can at least agree with that, but who knows what jimmies I’ve rustled

Vanishingly few apps work fully offline and they tend to be the ones that don’t send a buttload of requests in the first place.

In my experience.

Brb updating my personal lexicon

Well time will tell won’t it, but we’re both just guessing at the end

No that’s way too paranoid. Honestly 20 years not 6 months. And by then ladybird will be viable so nbd