this post was submitted on 07 Jan 2026
857 points (97.8% liked)

Technology

78511 readers
2905 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] silasmariner@programming.dev 0 points 2 days ago* (last edited 2 days ago)

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.