I'm old school. I still use a programmer's editor and the command line. I've used various versions of IDEs over the years and they all eventually boil down to the same thing: I feel like I'm typing in mud because of all of the hooks they put on my typing. If you are used to having this be a non-issue, like zero latency, don't even think about it, for 25-30 years, typing in an IDE is really painful.
"You could turn off the options and then it would be faster!"
Yes, and then I have basically a programmer's editor with refactoring support.
And on refactoring, I've found that the projects that I actually really could use that support have so many classes and multi-projects, etc. that it takes over an hour just to index it so that the really cool stuff works. Then I'm inundated with a sea of stuff that is not so easily searchable. It felt like Intelli-J has the best support here but that was exactly my experience. 2 hours to index all of the projects and then another 2 hours to sift through the results for actionable information.
So, I use a programmer's editor (which could launch things like gradle) but then keep several command line windows open in different projects. Edit this file in Sim-math, start the build there, flip back to the editor to edit some other file, recompile that project, fix the sim-math release notes and start a release, flip back to the editor and keep working on something else... and so on. All the time being able to see all cascading command line windows' left margins to track the progress of all of them.
It just fits my style better and to me certainly makes it easier to work on half-a-dozen projects at once.