(Transparent Thinking:
Http://gigix.blogdriver.com
)
Ten years ago, Ide is a luxury; after ten years, easy to use interface, strong function, fast speed is no longer able to touch the eyeball of Jolt Awards. The current IDE should bring some more things - more marginal value, this is the reason why JBuilder and Visual Studio gradually fade out Jolt Vision: The things they provide are still great, but they are not enough.
Eclipse is first a powerful IDE. For IDE (accurately said, JDT), it is a good winner with JBuilder. In some ways (such as support for JSP and EJB), JDT itself is not as good as JBuilder, so many people have suspicious attitudes to Eclipse.
Martin Fowler says two attitudes of software development
(Http://martinfowler.com/bliki/softwareDevelopmentAttitude.html). Most IDEs have selected Directing Attitude, that is, all functions required by users in an all-in-one environment. If you have new needs, please tell Borland, we will consider adding a feature in the next version - of course, or you may not pay attention to you, because you need too much. But Eclipse chose Enabling Attitude: It provides an open platform, an opportunity to participate, and some overall rules that need to be observed, then you can enjoy your talents, use Eclipse developers to use Eclipse . If you have new needs, you don't have to be polite, you will be a plug-in good, which will be the contribution to the entire Eclipse community.
Each of Eclipse has three important principles:
Invitation rule: As long as it is possible, try to invite others to continue to contribute to your work. Fair Play Rule: For a feature, all users follow the same set of rules, including the author of this function. Integration rule: New features should be tried to provide both environmental integration, providing a unified user experience, not to look into the grid.
These three rules ensure that the entire Eclipse platform grows in a "free city" manner and has always provided familiar and consistent user experience. In fact, most Eclipse's complaints only have not fully utilized other people's contributions. For example, JSP and EJB, Lomboz (http://sourceforge.net/projects/lomboz) have provided good support. I have even found a portlet for visual development JSR-168 compatible portlets, I believe this is not possible for any other IDE. This is only the glasses that will appear in the Open Source community.
In addition, Eclipse's "micro core plug-in" mechanism actually provides developers with a lot of possibilities, the only limit is just your imagination. For example, you can use the entire Eclipse Workbench as the GUI foundation of the Desktop Application, which is developed above its own business feature. Even if you don't like SWT, you can use the Eclipse as a component container, use Workspace as a resource container, start to do your own GUI.
