Everyone would have faced this hurdle some time or the other. It is difficult to change; it's even more difficult to change others. Be it changing your favourite shell, IDE, version control system, release process ...etc. or in the real world - changing city, habits… name anything. Here is a simple list of the arguments put forward against change and what I typically feel about them.
Argument: I'm used to X. I'm comfortable with X. Why should I change? Fact: In most cases it's nothing but pure laziness. Experimentation; have an open mind and be ready to try out things without any prejudice. Make it a fun cool thing to do and enjoy yourself. The flip side is that you might end up, or perceive as, wasting your time once in a while. I'm sure most people can easily identify those that aren't worth a single unit of their time and push it out. Anything above that is definitely a learning. If not switching/changing your favourite, you'll most likely get an idea of what features are good in your favourite and that's an important and necessary condition to becoming an expert. Argument: I'm an expert at X and I don't want to learn Y Fact: Most cases you would have falsely assumed yourself to be an expert. If you are reasonably expert at X you would have by now realised what is good and more importantly what is bad with X. Only knowing the deficiencies and shortcomings of your favourite fully qualifies you to be an expert. (The real gurus would have not just identified the issues but would have also fixed them. They are people who can be the change.) When Y comes along claiming it's better at features a, b, c ..etc. of X the real expert would quickly realise that Y is what they have been waiting for and would jump ship. It's not that easy to jump or switch habits of course, I'll come to that. Argument: What if the alternative is actually not as useful to me as it seems? Blah, Blah, Blah ...etc.Fact: Fear of change. People use shallow arguments when they are afraid of change. This is actually the biggest problem of all. Most people I have worked with in my past or present company are some of the brilliant minds I have ever met. Most of them are experts in what they do and very clearly understand their craft. These brilliant people in most cases vaguely know that the new (not as in shiny new; new to you, new to me) cool stuff is actually not just cool but also better than what they currently use. A couple of my personal experiences are with Eclipse vs. IDEA and SVN vs. Git. But they won't just be ready to try out the suggestion.How to overcome this fear? There is no straightforward answer. I'm no psychologist ; but I would say face it head on. Just go try it out. What is there to lose anyway. Try it in something minor, something with limited scope but go try it out. Argument: It's so hard and painstaking to switch.Fact: Yes, it requires determination.Once you are convinced that you are better off with the alternative it boils down to determination. When that determination is achieved it's about systematically learning the new stuff or unlearning the old stuff. Your determination will guide you through the rest. Suggested reading: 'Who moved my cheese?'