8 ms·
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 interfac
by throw-the-towel 1mo ago
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.
- bbkane 1mo agoEntropy finds a way :)
- zimpenfish 1mo agoYeah, 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.
- pstuart 1mo ago> Go people were always been perfectly capable of creating abominational messes before generics arrived A poster child for this is k8s.
- yencabulator 1mo agoFamously created by Java people, not "Go people".
- pstuart 1mo agoYes. It's a textbook case of trying to force your favorite language in rather than embrace the idiomatic use of the language.