There is a difference between not knowing the latest and greatest, and not keeping yourself updated with the evolution of your tool of choice. Most people will do the former after a while. It's too much time spend with too little gain. The latter however is not acceptable. I want my developers to know about the latest version of .net, and if they're not using linq they're doing it wrong.
Indeed. Pioneers are the people with arrows in their backs. For a stable system it's reasonable to wait before adopting change; especially if large areas of the existing system are built with a previous technology. Moving to new changes results in internal inconsistency, and possibly problems at the boundaries.
I never stated all evolution should be followed blindly. But once the evolution becomes established as best practice, there is very few reasons to not do it.
But 8y ago WCF was marketed by Microsoft as the future of web services. It was clear to me from the outset that it was a mightmare to configure and unecessary complex. Now I think it is the generally accepted view. But if we have to wait 8 years for each new technology...
