The really odd thing about the original statement is that this guy "can't imagine" working without generics. That is a remark that could only be made by someone who is fixated on modeling all problems in terms of type systems.
I can see myself making that statement, and obviously "can't imagine" is hyperbole, since I've written a lot of C, but I can't imagine taking seriously a new language that doesn't let me reuse data structures. I'm not sure what you mean by fixated on modeling with types.. I don't care about inheritance hierarchies, I just want a priority queue (and a multimap and a graph and a blocking queue oh wait that's yet another built-in special case) that doesn't force me to downcast like in Java 1.4.
"Show me your code and conceal your data structures, and I shall continue to be mystified. Show me your data structures, and I won't usually need your code; it'll be obvious."
-ESR, paraphrasing Fred Brooks
What I find odd is that he makes this statement, but then doesn't explain which of the following he prefers:
1. Rewriting algorithms again and again for each minor variation of a data type
2. Downcasts everywhere
3. Contorting code to work with the two magic data structures, array and map
Instead he goes on to rant about type hierarchies, which is awfully non-sequitur.