3 ms·

I'm of 2 minds. I come from a Java background so I've personally wanted generics. ORM's are 1 use case that comes to mind. But. There are many modern langua

by libria 8y ago

I'm of 2 minds. I come from a Java background so I've personally wanted generics. ORM's are 1 use case that comes to mind. But. There are many modern languages that already have generics. Why can't Go be that one that doesn't cave in and remains powerful in its niche and perhaps may never be the preferred tool in other areas? Why must it be useful for web development, microservices, DAL, etc.? Any implementation of generics in Go will come with complexity tradeoffs. I feel like the community learns more about languages and software engineering when we maintain language diversity and see the pros and cons of each approach in practice. I want generics for selfish reasons, but would also like to see how a modern strongly-typed language solves problems without it.

idle_zealot 8y ago
As someone who quite likes generics, I'd love to see how a modern strongly-typed language solves problems without them. And I think that's what the Go community and developers have been trying to do up until now. It looks like they're giving up. I'm not sure whether we'll ever find another way to tackle composition/scalability as effectively as generics do, but such a technique would be fascinating to see.