> Me: Nothing has ever made me want generics in Go the way that the telepresence2 codebase has made me want generics in Go.
> CTO: Is this because of the problem domain or the incidental structure of the code?
> Me: I'm honestly not sure. I want to say the incidental structure of the code, but I'm not sure how else I'd structure it.
I implemented codegen/template based generics, but eagerly await being able to replace that with actual generics in Go 1.18.
So, I guess the lesson is that it's easy to write off it off when it's someone else having the problem?
In 2002, Visual Studio T4 was used for generating .NET code shortly after it was introduced.
In 2005, Eclipse EMF was used for generating Java code, eventually Java 5 made that unnecessary.
As you see, that is a path well known for the last 30 years.
Eagerly waiting for Go 1.18, even with CLU like generics.