You could also say that a command line terminal is just a wrapper around the OS's process start function.
But in all seriousness a good IDE is much more than a text editor and buttons which run terminal commands. The main thing a good IDE has is a good debugger, which not only allows for stepping through code easily, but also shows the values of variables, memory, registers, in one easy to use interface.
If you don't use a debugger then either you're only building very simple programs, or you're stuck in some sort of special hell when it comes to debugging.
Oh, true, debugging affordances as well. You can also use a debugger from the command line, though—the IDE is wrapping terminal commands, or at least wrapping a library and providing functionality equivalent to that library's terminal client.
I never got in the habit of terminal debugging, but I'm sure some people prefer it over using a GUI. I'm that way for git: The command line interface is unintuitive, but I've gotten accustomed enough to it that it feels comfortable.
But in all seriousness a good IDE is much more than a text editor and buttons which run terminal commands. The main thing a good IDE has is a good debugger, which not only allows for stepping through code easily, but also shows the values of variables, memory, registers, in one easy to use interface.
If you don't use a debugger then either you're only building very simple programs, or you're stuck in some sort of special hell when it comes to debugging.