[onetimePete]

IDEs are either swaggering monoliths, where all complexity has been hidden away in a labyrinth of options- or a small basic set, that waits for you to be turned into such a custom tailored to your taste monstrosity.

Sad thing is, really new interesting features are rare. There is no deep learning IDE that watches you debug, and associates source code by changing variable X fixed bug in file Z via time of change correlation and instruction flow graph.

There is no real approach to layered responsibility. Meaning, a beginner should be allowed to change functions, but not add classes and interfaces to existing well structured code, without the author signing those "big" changes off. This crucial "zoom out into algorithms and architecture" and drop back in to display details- still often happen via external tools, as the IDE is not able to abstract Information from the actual sourcecode away.

Finally - debugging and Unittests, these are actually highly automate-able task- yet here im stepping it, even though by now at least conditions can be attached to the various execution paths.

Finally, no ide has a "User" Simulation, to detect crappy requirement engineering before the whole thing is gone into software. A proportioned team of simulated "persons" and "use-situations", that gets to traverse a draft of the gui and the workflow should detect hotspots and annoyances, and avoid a lot of unnecessary & expensive itteration.