Emacs and LLDB

There are certain codebases where IDEs work well, and certain codebases where they don't. In either case it is certainly possible to code using a text editor and not lose much productivity; you just need (for example) DOxygen in a web browser so you can quickly look up API calls. Is it exactly equally as good, no, sometimes it's better and sometimes it's worse. I used an IDE in a project where I added stuff to the Java compiler and it was a boon to be able to use IntelliSense to find the right API call. I didn't even consider it with my current Python project because Python doesn't provide the static typing needed for anything like IntelliSense to even work.

This is just a dumb argument, partially because you can shift goalposts by calling Emacs an IDE or SlickEdit a text editor. I personally don't like setting up projects with classical IDEs and find they can be very brittle sometimes, but I'll use them when they're the right tool. But even if I didn't, I could get by fine without them, and I expect most good developers could, too. Browser-with-autogened-docs can replace most of the advantages, especially if you have two monitors. So, it really comes down to personal preference, so let's not argue Vi versus Emacs in its modern incarnation.