The main reason I've left IT jobs is due to management problems, but in the background technology has been a reason I was glad to leave them. You might be thinking of this in a different sense. I look at it from a language/API standpoint, not the IDE. As long as you have a command-line compiler and debugger available, you can always get away from a bad IDE. You have to work harder at what you do, but you have more control over the environment.

This won't apply to most developers, or even many development situations, but it's possible to design your way out of a bad situation, and this goes back to my motto of, "It's a matter of how you use technology, not the technology itself." It's more a matter of time than technology. Do you have the time to improve the design of what you are working with? In a lot of situations you don't, or even if you do, the people who come after you may not understand it.

I've told you this story before. I was working on an ASP.Net app. for a customer several years ago. I was using VS.Net's design tools to create what for ASP.Net was a complex web page, and I painted myself into a corner. I got the job done, but it was a total mess internally. I realized later that I could've made the design more sane if I had avoided VS.Net's design tools and created my own class framework to abstract away some of the complexity. I had a chance to do that for a different page in the same app., and I was a lot happier with the outcome. However, I realized there was a reason .Net developers liked programmable code generators. The design made a lot more sense, but the code got very repetitive, and I had to do it all by hand (unless I wanted to use my own money for a code generator, which I didn't). I didn't have time to create my own generator. Just typing out the code (along with copy and paste), while boring, was faster.