I'm a vim user, not an Emacs user (though I have dabbled with emacs before). If you still use vim on the console, you can do a lot better.
There's a reason why vim has support for multiple buffers. That you can keep multiple files open simultaneously. Read about vim remoting, and you can use a single gvim instance (which offers better performance and font rendering), and edit all files in just that.
Even in emacs, buffers are everything. Nobody opens a new instance of emacs for each file.
Actually years ago I discovered one bewildered undergrad would run Emacs to edit a single source file, control-Z out of it, run the compiler from the shell, test, start another Emacs (after all, the shell announced the previous Emacs was "stopped"), lather-rinse-repeat until the shared host had finally died under the weight of all the suspended Emacs processes.
To sum up, nobody sane opens a new Emacs for each file. VISUAL=emacsclient is your friend, as are Dired and M-x compile....
There's a reason why vim has support for multiple buffers. That you can keep multiple files open simultaneously. Read about vim remoting, and you can use a single gvim instance (which offers better performance and font rendering), and edit all files in just that.
Even in emacs, buffers are everything. Nobody opens a new instance of emacs for each file.