&quot;Computer scientists&quot; don&#x27;t have an opinion much about <i>a</i> particular IDE; if you want that functionality in an IDE, it might be a shorter path to cause it to exist in the first place.<p>I bet it&#x27;s harder than you think.<p>Also, IDEs are better than they used to be - I stopped using them because they caused problems in the late 20th Century. There was a proliferation of them until Eclipse got good enough to not cause problems. Eclipse still had less text editing power than some just-plain-old-editors from the 1980s. So I only use an IDE if it&#x27;s the only logical choice for a development system. It usually isn&#x27;t.<p>If, as in one shop at which I worked, you constantly write, say EMACS macros and use them a lot, you will evolutionary drift away and it will make your team more and more ... linguistically isolated, which has costs in onboarding and this sort of  mild narcissism about <i>your</i> setup.<p>I think that dependence on an IDE is mostly a weakness, not a strength.