Type parameterization is a useful concept, and it even found its way to Java and C#. I’ve found a nice technical comparison, a must read for C++ template aggrieved veterans who waited a long time to move over. And geeks surely will enjoy the implementation paper for C# :)
But before going over to the Java vs. C# language wars, read Joel’s opinion first, so you will finally see that most arguments are nonsense if you need to solve real world problems. But wait! I personally hate Java, probably because of the related glorification of the “free threading model” that drove me nuts after I consumed this book, or some methods which were never implemented, or always broken and then considered deprecated. To be fair, I’ve not found a stable sort in the .NET API and the return value of binary search is surely something that will create a lot of short term headaches, ... unit tests may help to retain your sanity.
C#3 extension methods support you to build internal DSLs or to finally convert all your code into plain English. Soon we will find all the crazy stuff that made Haskell so alien in the language near you.
Confused about all the paradigms? This diagram gives you an overview. But the real thing we developers declared war on, is complexity, methods to reduce it are existing, but the decision when to use what is yours.
yours
armin