2 ms·
> It's not that I don't see the potential benefits of static typing. I just don't see the cost-benefit being that compelling. Now you are not talking about gen
by barrkel 17y ago
> It's not that I don't see the potential benefits of static typing. I just don't see the cost-benefit being that compelling.
Now you are not talking about generics in Go, but a major philosophical position in programming language theory. I think your question is disingenuous. It is because you don't understand why some people prefer static typing that you don't understand the need for generics. Until you do understand that, you'll remain unenlightened with respect to generics.
- stcredzero 17y agoNow you are not talking about generics in Go, but a major philosophical position in programming language theory. I think your question is disingenuous. Specifically, I'm asking about people's actual experience. My question is sincere. I am not interested in people's preferences or their "philosophy". What is their experience? Also note that I allude above to having cursed the lack of types in Smalltalk at times. This doesn't seem so significant for collections. I'm asking: Is putting the wrong thing into a collection really such a big deal? What is the actual experience? I gave mine. What's yours? EDIT: Wow, it seems like just mentioning "static typing" should now be included in "Godwin's Law"! Rational discussion has become impossible!