People have different needs, and I get reminded of this when talking about editors/IDEs with others. Had a friendly 'discussion' with a dev a couple years back

People have different needs, and I get reminded of this when talking about editors/IDEs with others. Had a friendly 'discussion' with a dev a couple years back who was leading a discussion group and publicly scoffed when I mentioned I'd picked up IntelliJ. He went on to talk about his company's code and how 'lean' it was and how they didn't need any 'heavyweight' tools like a Java IDE. I asked him about the code he was working on. How much of it did he write? "A lot". How much was written by people at the company "100% in house - we write everything from scratch". OK, great. Working on the exact same codebase with the same core team for years on end (2+ years in their case), you probably know every single bit and byte by heart - awesome. Very few of us operate in that world. Many of us come in to codebases where we didn't write every line. The original gone, hostile or possibly even dead at this point. Full-featured IDEs (the guy in question kept gushing over sublime-text and how fast and lean it was) provide another level of code insight that basic editors don't provide (not ragging on ST, just pointing out it doesn't do what I need for the breadth of projects I work on). I think the OP needs to look deeper at the tools he's criticizing before writing them off. His ctrl-f example demonstrates that he doesn't seem aware of other IDEs that provide this (and... I'd probably use ctrl-f to find something, not fork). In the vEdit example, we get 'what file do you want to open?' That's generally precisely what I don't want to think about when I come in to a new project, because I want a visual overview of what's available. I want to see the naming convention, the layouts, note what's available and what's not. Removing that in an effort to be 'simple' hinders a heck of a lot of automatic project discovery for the sake of ... what? 'Simplicity'?