some years ago i did all my coding in vi, then later in emacs. i still believe these are great editors; i just dont use them anymore for java development, especially j2ee application development. im much more productive if i use an ide whose sole purpose in life is to facilitate product development. i can probably still write code faster if i use vi. however, i doubt i could meet my deadlines if all i had was a tool that was primarily meant to be an editor. emacs is a great environment for setting up and using a development environment. however, it is for all purposes a code editor, not an ide.
developing distributed applications is a complex process, and developing the components that make up the application requires coordination and integration of different design and development environments. the software development cycle for the release of a product warrants the use of data and component modeling tools; sophisticated code editors; a fully integrated compilation and build environment; deployment tools; fully integrated debugger, unit, and integration testing environments; and source code version control. nowadays, you have two options when developing j2ee software. one, use your skills to create a development environment that can use tools from different vendors cohesively and effectively. ... 下一页