News for hackers. Stuff that matters.
Re:Generic Methods in Go 1.27 by throw-the-towel on Thursday August 20, 2026 @01:37PM (#49377710)
I remember my coworkers having managed to write Java in pre-generics Go. The code had functions wrapped in functions wrapped in yet more functions, and interfaces only ever implemented by one type to replace the generics abuse. Life finds a way.
Re:Generic Methods in Go 1.27 by zimpenfish on Thursday August 20, 2026 @02:11PM (#49378123)
Yeah, Go people were always been perfectly capable of creating abominational messes before generics arrived. Once you've looked at an interface referencing an interface referencing an interface referencing an interface which is only ever instantiated by one (1) type, you realise that all hope has been lost and your only recourse is blatant sarcasm, pointed replies on Slack[0] and PRs, and finding the perpetrators after dark with a big sack of flour.

[0] Other corporate messaging systems are available.

Re:Generic Methods in Go 1.27 by pstuart on Friday August 21, 2026 @09:40AM (#49387908)
> Go people were always been perfectly capable of creating abominational messes before generics arrived

A poster child for this is k8s.

Re:Generic Methods in Go 1.27 by yencabulator on Saturday August 22, 2026 @11:25AM (#49400721)
Famously created by Java people, not "Go people".
Re:Generic Methods in Go 1.27 by pstuart on Saturday August 22, 2026 @12:25PM (#49401256)
Yes. It's a textbook case of trying to force your favorite language in rather than embrace the idiomatic use of the language.
Re:Generic Methods in Go 1.27 by bbkane on Thursday August 20, 2026 @01:50PM (#49377859)
Entropy finds a way :)