> Erased generics the type information is not available at run time. That's the way Java does it and it kinda sucks.
In a good statically-typed language you don't need runtime type information. It could be a Void in the bytecode for all I care, as long as it behaves correctly.
> obj.GetType() == typeof(typename)
In a statically-typed language, this can be optimised away to a bool at compile time.
Oh absolutely not true AT ALL.
Occasionally it is really useful to be able to do something like `new T()`. Without reified generics that is not possible.
new T? What's wrong with the old one?
Jokes aside, what's the use case for not knowing what T is until runtime?
Pretty much all polymorphism works by not knowing the concrete type til runtime. If you have an Animal reference to a Dog instance, any method you call on it is resolved at runtime, because the reference knows the type. Reified generics do the same for type parameters, whereas erased types are only used for type checking at compile time.