It depends on the language. With Java, I get a huge return because the IDE can take care of so many mundane things like getters and setters. Java also sometimes has odd names used in its standard library (for example, you use queue.offer() and queue.poll() to add and remove things rather than something like 'enqueue' and 'dequeue' or the standard push/pop. An IDE prevents me from having to deal with looking it up constantly.

With Python and Ruby, I find a text editor sufficient and usually I'm doing web work with those languages which is perfect for vim/emacs over SSH.

PHP tends to have a huge library of builtin functions and it uses positional arguments (you can't call a function with arguments out of order denoted by keyword like python). I've found an IDE to be helpful for PHP in the past. SQL isn't a big language. As such, I can't see an IDE helping. JavaScript, with libraries becoming the preferred way to code, doesn't seem like an IDE could do much unless it understood the library.