This guy is having a hard time getting over the fact that his solution for adding generic types to the JavaTM Programming Language didn't win. On his continuing rampage to discredit the winning proposal type erasure (GJ), he visited the Eastern labs only to reveal that he has no clue about the problems type erasure is addressing.
Lacking innovations of his own, he now is trying to make a career out of stating the obvious (not having full reification is bad for reflection and serialization) and presenting half-backed solutions that any graduate student can produce. Furthermore, he seems proud of not having read the latest Java Language Specification.
Neal Gafter has explained why Sun went with erasure: Puzzling Through Erasure: answer section. My question to the good doctor is if Neal Gafter can state the problems so clearly, how come you can be a Professor and not even grasp them? I dare you to present a reified solution that achieves backwards compatibility and migration compatibility.