> I'm with you on that. Erasure introduces an unnecessary duality in the > type-system where you read one thing, but the compiler and runtime > really sees something else!
Except it's arguably necessary for backwards compatibility. > At least in C#, you get what you see, plus they can do a whole lot of > performance optimization and code sharing. The code is always shared in Java as there's only one copy of it. > Sometimes it's ok to draw a line in the sand and break with > comparability to fix something, Java could be much much more elegant > and lean today. If you have a valuable community who uses the word 'enterprise' as a positive thing, you don't want to be invalidating their old code. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
