News for hackers. Stuff that matters.
Re:How generics were added to .NET by enitihas on Monday March 05, 2018 @06:47PM (#16525658)
Java didn't handle it much better, they simply chose a different tradeoff. They chose to implement generics via type erasure, which basically means List<String> and List are the exact same classes at runtime.

.NET chose to implement specialised generics. Many people think that is a better tradeoff.

Re:How generics were added to .NET by KMag on Monday March 05, 2018 @08:02PM (#16526058)
Note that Java's originally only generic type, the array, has C#-style reified generics. The early JVM implementors should have felt a bit dirty in providing reified generics support for arrays at the VM-level without at least having a forward-compatible VM-level provision for general reified generics.
Re:How generics were added to .NET by mwkaufma on Monday March 05, 2018 @11:37PM (#16526890)
See also: syntax-baked reified arrays, slices, maps, and channels in go (but "no generics" right?)
Re:How generics were added to .NET by Someone on Monday March 05, 2018 @09:04PM (#16526331)
I think they made the right choice at the time. Targeting devices smaller than desktop computers about 5 years before C# (in a time when Moore’s law was in full swing), they had to cram the jvm in much smaller systems than C# targeted.
Re:How generics were added to .NET by int_19h on Monday March 05, 2018 @09:24PM (#16526405)
C# did the same exact trade-off in 1.0.