As someone who is leaving my current job in large part because it forces me to work in a godawful web-based IDE, I think you need to think really, really hard a

As someone who is leaving my current job in large part because it forces me to work in a godawful web-based IDE, I think you need to think really, really hard about your motivations here. What problem does an IDE webapp solve which can't be solved any other way? Also, what problem does an IDE webapp solve which is so terrible, such an impediment to progress that it justifies throwing out the decades worth of development tools and experience we have on the command line or in traditional IDEs? Honestly I've yet to come across such a problem. And any such benefits my company's internal web-based IDE might provide are entirely outweighed by the loss in productivity that comes from no longer having access to diff and patch and Unix pipes and vim and Git and all the other tools I've become entirely accustomed to on the Unix command line. Honestly, a MindTerm applet and a Unix shell account on a remote server would be a more functional "web-based IDE" than any I've seen, and certainly more functional than the one I'm leaving. Obviously given enough time all of those tools could be replicated in a web-based environment, but why even bother? What's the killer app here?