Those are single-OS editors, aren’t they? If it can’t do at least three operating systems, again it is not really worth my time to develop expertise in it. If I need to code on a mac I’ll just use vi, because that is available on HP-UX, linux, Suns and various BSDs (and has an implementation in busybox so it’s by far the most likely editor on embedded systems). Learning how to do something in vi is at least five times (really, more like ten times) as effective a use of my time as learning to do something that will only work on a specific OS.
Basically learning editors is a low value activity compared to using them, but learning them makes using them more effective, so you have to find the sweet spot for your own trade… I do more systems integration programming than app programming, so single-OS editors are a bad investment for me. I’ve probably used 25 different editors professionally so far. Maybe more ¯_(ツ)_/¯ I no longer bother with debuggers or IDEs at all, I gave up on them decades ago because they just slow me down.
I agree with and endorse this!
