Take a look at COBOL in our daily lives. The switching cost is horrible and lets face facts, developers don't seem to want to develop the next cool version of

Take a look at COBOL in our daily lives. The switching cost is horrible and lets face facts, developers don't seem to want to develop the next cool version of COBOL. I sometimes wonder about switching costs when you have two or more groups that have different beliefs, practices, and views of the daily grind. Infrastructure & Software costs money and time to switch with no real personal benefit and requires a change in knowledge. Both your examples require a hard switch and don't have a nice easy transition plan. Add taking away things that are familiar to the people in the field and you have a bad, long transition.