That's not the situation I've described - punch cards disqualify.
The situation I mean is where developers insist on writing software on version X, which doesn't compile on X-1 and is buggy on version X (and might not compile again on X+1). For a concrete example, new C++ features that aren't correctly implemented and lead to harder to read code and worse error messages when applied to day-to-day problems (which these features were never meant for).
To have progress we need to change things. When we change things, we may break things, regardless of tests.
To quote deijkstra: "testing can be a very effective way of showing the presence of bugs, but it is hopelessly inadequate to show their absence". From 'the humble programmer'.
Production is the only way to eventually discover the stability of any software, even with 100% test coverage. It's a necessary evil in the support of progress.
Software needs to be tested. But your view that the whole world needs to jump on it at once is very black-and-white.
If developers want to use newer stuff usually they have a good reason. The ability to hack around the deficiencies of old dependencies does not mean that one couldn't get a better, cheaper solution with newer technology.