The choice of IDE is the main first, if you started from JBuilder, it is all in your eyes, and its shortcomings can be inclusive, and the masters will not have any prejudice for mainstream tools.
I have been in Delphi, and I should prefer to choose Borland's products, but I first engaged in J2EE project, the company is a pro-IBM system, WebSphere VisuaLage, and later Eclipse, there is no reason not to love it.
Two versions are left on the machine, while using, 2.1.2 and 3.0.1, the low version is still used.
2.1.2 The case is as follows: Easystruts 0.7 vssplugin_1.5.0 (no way, the project group VSS) Tomcatpluginv3 Lomboz together for Eclipse 6.2 3.0.1 Mainly used with MyECLIPSE 3.8.2 replaces the original TomcatPlugin / Lomboz / Easystruts. This Dongdong is indeed strong. After all, it is a commercial product level. The JSP editor deployment is very convenient, there is one, too performance. My machine is P4 1.4G, 512 memory, when running Eclipse 3.0.1 myeclipse, it is obviously tight, the system does not stop in Building Workspace, and its JBuilerx, which is just colleague. Is it tolerable, can't bear it? In addition, the stability is also poor, and the annexever must restart the IDE twice due to memory overflow. Under the trade-off, I would rather use the 2.1.2 version, the pursuit of the version is not necessarily the latest, my main workload is still in the design and implementation of Java components, with 2.1.2 speed and stability to sacrifice Code assist and JSP editing is still worth it. As for why it doesn't use 2.1.3? It is very simple. I have been practicing, 2.1.3 Support for TOGETHER For Eclipse 6.2 is not very good.
