JRebel is really an amazing tool.

Given the nominal cost of JRebel and the huge amounts of time it saves, I would not consider developing Java EE applications without it.

Since introducing JRebel to our Java development teams, we have not only seen a 30% increase productivity, but also a marked decrease in service requests due to software faults. Our teams can now focus 100% of their attention on development without being hindered by the J2EE cycle Build and Redeploy steps.

Setting up JRebel was completely painless and my questions on the support forum were answered quickly. The performance gains were immediately obvious to us, so after the evaluation period was over we decided to purchase licenses for all our developers.

You mean you haven't tried JRebel already! How could you have survived this long as a Java developer without it!

It's so good I sometimes forget that I'm using a crappy toy OS (Windows) on poorly spec'd hardware with a painfully slow app server rather than Tomcat on OS X.

Every delay sucks, so whatever causes less delays rocks.

Why isn't JRebel part of the standard Java SDK?

JRebel is an awesome product. I probably save 3 hours out of a 6.5 hour workday using JRebel - I use Eclipse with JBoss and it saves me a tremendous amount of time by not having to restart JBoss every time I make a change.

Stopping and start my container 10 times a day is the most annoying thing in the Java world. Finally I hope I have found the solution with JRebel.

I just hated the whole Eclipse IDE and one of my co-workers suggested I try Jrebel since 40% of my time was waiting on Eclipse to build and run. With Jrebel, things are going much smoothly now.

JRebel has transformed a nightmarish 10-minute modify, compile and debug cycle to a matter of seconds. Thanks for giving me back my sanity.