The libraries will, yes. But folks just using the libraries still won't need generics. If you know your concrete types, they're just not that useful. Even in

The libraries will, yes. But folks just using the libraries still won't need generics. If you know your concrete types, they're just not that useful. Even in home-grown libraries, I find generics to be a convenience rather than a necessity. It's useful to not have my library code so tightly coupled to my non-library code. But it does also come with a cost: every so often I have to check what the library actually does because being loosely coupled meant that iterations in the rest of the system didn't automatically have to involve the library, so the library code can get left behind.