| It's not remotely unique to sysadmins. If anything, devs are worse. Have you seen how many Python 2 packages there still are out there? How often do we see opinions on HN that amount to "C > *" whenever Rust, Go, Java, C++, etc. are in the submission? That's the exact same "resistance to change". Change isn't a light switch. It doesn't go from 100% old to 100% new. Change is a long, slow, time consuming, and difficult process that requires extra effort at every stage in the process. There are several different stages: 1. Not knowing the new and being confused. 2. Identifying the new and having to develop special processes. 3. Accepting that the new is here to stay and translating or adapting the processes and procedures from the old, and spending effort to re-learn the same features in the new system to maintain business as usual. 4. Discovering all the new ways that the old process doesn't fit the new system or the new system isn't designed for your existing business processes, and fixing them one catastrophe at a time. 5. Running the old and new, simultaneously, for the lifespan of the systems that depend on them. 6. Having the new significantly overtake the old such that it's now unusual, and being frustrated that the old still exists. 7. Forgetting knowledge of the old via atrophy. 8. Encountering the old and being confused. And that's when the new system proves itself to be better than the old. |
Pretty much none. Can't say exactly how many, since http://py3readiness.org/ is dead.