Good bye MyEclipse. Welcome STS -Spring source Tool Suite
I had been using myEclipse for couple of years and was happy with features and convenience they provided especially the hot deploy feature. The license fees is $30 per year which wasn’t bad.
Recently I downloaded MyEclipse7 which had some new features and like advanced java script tooling, JSF views and enhancements. It was a huge file and after installation when you start myeclipse, it takes a good amount of time to fire up.
I have a machine which is pretty good with 2GB of RAM and this was not the kind of sluggish performance which I expected. I am assuming the high boot up time is that they have introduced many new features and capabilities, UML upgrades . Now even if you are not using them , it takes time to load them up all the libraries. Perhaps they should have allowed the users to customize the options based on need instead of pushing everything in their face.
I thought of shifting back to old version of myEclipse6.0 . Then I read about Spring announcing Spring Source Tool Suite 2.0
Spring source tool suite is built over Eclipse. Spring claims that STS will improve the developer productivity especially with the new Visual Spring Configuration Editor. It is ironic that with Spring 3.0, we are moving towards annotation and the xml files are just bare bone skeleton.
The reasons because of which I moved to STS because of its capability to integrate with Spring source TC development server (build on top of Tomcat). What you gain from STS and with Spring source TC development server is the ability to monitor the performance of your code. I will cover how to do this in next post but in the meantime I am happy with what I see in the STS.
I need to explore what could be issue.
But anyway, overall I am satisfied with Spring source tool suite.
Good bye MyEclipse and I get to save $30 !