Java Development Is Up For a Change
Disclaimer: I’m affiliated with the product and this might be taken as a commercial but nevertheless things will start to change.
Before moving to Java (mostly JEE) I did couple of years PHP development. The thousand levels of abstraction, tons of third party libraries and most importantly the ever taking change-check cycle were something difficult to accept. I was so used to getting feedback automatically and could not even imagine that one day I will even have to re-traverse some application just to store some state.
For the past months I have been working on team battling the change->compile->redeploy cycle. Today there is a release. It is called JavaRebel and the product brings the cycle down to change->compile->check. Classes loaded by the container can be changed and JavaRebel inbetween will load these changes (adding/removing/changing fields, methods etc.).
When I was working on my Google Summer Of Code project I had to buy extra RAM just to be able to run couple of instances of Eclipse. I was not willing to buy a new CPU to make the restarting these instances of Eclipse faster. JavaRebel does not have Eclipse support but it is in the roadmap.
There is a screencast up that will demo some features of it. Java development will change.
google » Java Development Is Up For a Change said,
October 8, 2007 @ 9:53 pm
[...] Check it out! While looking through the blogosphere we stumbled on an interesting post today.Here’s a quick excerpt Disclaimer: I’m affiliated with the product and this might be taken as a commercial but nevertheless things will start to change. Before moving to Java (mostly JEE) I did couple … . There is a screencast up that will demo some features of it. Java development will change. [...]