Personally, I haven't worked with any senior engineers that weren't opposed to new technologies. They were just very skeptical because they have been burned so many times by the empty promises and worse, dealing with unintended issues that result because very rarely is the happy path ever taken. As we all know, it it the edge conditions that cause the issues because a generic frameworks many times cannot anticipate all edge conditions so they just don't handle it.
The young engineers are always ready to change for the sake of change many times, and they have never seen results when things go bad. They also don't seem to understand the full cost ($$$) of the situation of the upgrade. This includes the internal costs of testing as well as the potential cost to the customer for their internal testing. Rarely do I see a true risk analysis done which can be translated into a "risk versus reward" understanding of is the change worth it. All of this comes from experience: it just can't be taught, it must be experienced.