vi/vim is my editor of choice because the shell (ksh or bash) is my primary IDE. The last 20 years or so has required me to develop mostly scripting (ksh, sh o

vi/vim is my editor of choice because the shell (ksh or bash) is my primary IDE. The last 20 years or so has required me to develop mostly scripting (ksh, sh or bash) that is executed by some sort of automation. The shell is where I spend most of my time executing commands that need to be scripted, inspecting various system resources and troubleshooting. The vim editor is readily available to use in places where external tools outside of a terminal emulator may not be readily available or the startup time required to configure those tools may be better spent on configuration tweaks in the shell. I've also found especially when working with build automation in Jenkins or deployment automation with uDeploy, that a GUI-based client IDE somewhat obscures things I need to see in the environment I am building in. IDEs like Eclipse and IntelliJ IDEA, while providing plugins for Gradle or Maven, may have configurations that are not compatible or differ in some fundamental way from those of the server build environment.