> I am in and out of my editor 50 times a day, Emacs just can not and does not support this approach.
This is true. I think the typical approach with Emacs is to leave 1 instance open for a long period of time and just keep coming back to it. (This is what I do, anyway.) I don't think this is any worse in general than opening and closing the editor as needed, it's just different. Especially when you consider that you can run terminals/shells within Emacs, it's a completely inside-out workflow. Instead of:
1. do a bunch of stuff at the terminal
2. need to edit a file
3. open my editor
Once you've gotten to step 2 you're already in your editor!
Generally Drupal doesn't use a class or similar OO construct to manage it's organization of individual modules. Some of the various sub systems of Drupal are moving to more traditional OO structure (such as the database abstraction layer) and some module do as well, but it is definitely not required by the framework the same way that most MVC apps such as Rails are setup. This doesn't mean that Drupal doesn't/can't have a clean abstraction of presentation, business logic and routing, but it's not enforced in the same way that some other frameworks handle things.
This is true. I think the typical approach with Emacs is to leave 1 instance open for a long period of time and just keep coming back to it. (This is what I do, anyway.) I don't think this is any worse in general than opening and closing the editor as needed, it's just different. Especially when you consider that you can run terminals/shells within Emacs, it's a completely inside-out workflow. Instead of:
1. do a bunch of stuff at the terminal
2. need to edit a file
3. open my editor
Once you've gotten to step 2 you're already in your editor!