Reflection is the least of the problems this solves. The majority of the issues and gotchas listed in the generics FAQ for Java do not happen in C# at all. I

Reflection is the least of the problems this solves. The majority of the issues and gotchas listed in the generics FAQ for Java do not happen in C# at all. It is liberating. Reflection is an advanced use case that some people use, but it is rare. The lack of flourish in. NET overtime more to what happens when a company takes the reins of a stack and later stops working on it. Microsoft for a while invested and designed JavaScript, Python and Ruby versions for .NET. But when conditions changed, there was no interest to keep the projects going. These are all observations from an outsider at the time the projects were defunded. Because of the siloed approach to development at the time, and the lack of an external county around those efforts, bootstrapping a community to drive those on their own proved to be very hard. Ruby mostly died, Python is barely surviving. The mood in the ecosystem went from "we can build these and speed them up" to "this is an ongoing cost, let us rather interop with the real implementations rather than find constant catch up". Meanwhile, languages that Microsoft did not build did flourish, like PHP This corporate phenomenon deserves a blog post on its own