“Software is eating the world,” said Netscape founder and tech investor Marc Andreessen. Line by line, hardware is being consumed by code, and Java is spoken by a massive army of hungry mouths.
However, since the programming language was introduced in 1996, developers have had to write Java code on their own machines and then upload their code to remote servers for testing.
The idea that would become a glass of ice water to coders in redeployment hell was born in Estonia in 2006. That’s when Jevgeni Kabanov found a way to address Java’s core problem – the redeployment bottleneck. His insight led to a start-up and two products that smart Java teams wouldn’t be caught without. In other words, magic happened.
Developers at thousands of companies around the world use JRebel to instantly view code changes without redeploying the application server.
The result? Happy coders writing and testing beautiful code. Happy customers enjoying time and money saved through all that beautiful, productivity-boosting code.
Today, ZeroTurnaround is the labor of love by a global team of 150+. The company’s go-to-market heart beats in Boston, Massachusetts, while our development feet are firmly planted (and rapidly growing) in Estonia, at two offices in Tallinn and Tartu. We also have a branch in Prague, Czech Republic.
We are dedicated to making developers lives better, and we now have over 65,000 active users at 5,200+ customers, including 36 of the Fortune 100, in 80+ countries.
DEVELOPERS SAYING REALLY NICE THINGS
We’re developers who make stuff for people just like us. Yes, our software is used by companies, from startups to well-known multinationals. But at their core, our products are consumer products. It’s a stroke of good fortune that our “consumers” happen to be other Java developers. You know, people like us. Here’s what some of them have said about life with the tools we’ve made.
WHAT THEY SAY
Working with JBoss, Seam, JSF and the Eclipse JBoss Tools...It's very painful. I had read about JRebel a couple of times on theserverside.com and javalobby and decided to give it a try. It works great.
JRebel has the ability to change code dynamically when the program is running or during a debug session, which I have been looking for a long time. I am sure it will save a lot of development time, especially when the size of the project is large.
The developers at BlackBeltFactory.com use JRebel and although I probably could have gotten it for free from the ZT guys, I wanted to pay for this fantastic product.
I have been very impressed with JRebel, wish I had come across this product a lot sooner, would have saved me so much time/boredom waiting for so many container restarts.
Finally after seeing that JRebel won the JAX most innovative Java technology award, I am giving it a try. Sick of all the tomcat restarts.
I started using JRebel for web and server deployments on JBoss and I've been addicted ever since. It simply just works :-)
The time period between making a change, rebuilding, deploying and restarting the container has always been a sticking point with me, but JRebel allows me to develop constantly without bouncing back and forth. Personally, it's one of the more important pieces of software I've come across in quite some time.
I like the way [JRebel monitors] the file system for changes and smartly reloads Java changes into Hot Swap/Hot code memory. It just eliminated by build time during development by 90%.
JRebel has made my life so shiny happy. It auto deploys updated classes and JSPs. Holla!
Since migrating to IBM WAS 7.0, we've had trouble with replacing HotCode - we're now using JRebel for uninterrupted development and it's working fine :)
Jrebel is so awesome it almost hurts. Or rather, not using it hurts.
For the price, and for how easy it is to get installed and running in a developers’ environment, using JRebel is pretty close to a no-brainer.