Last night, while “watching” JavaRebel win a JOLT productivity award on Twitter, I couldn’t help but think, “how wrong is it that I’m awake at 3:30am (Central European Time), hitting ‘refresh’ in firefox, again, and again, and again – and getting a sense of excitement out of doing it?”
And then I thought – hey – this must be something like using JavaRebel for development, without having to deal with application restarts, just coding in in a continuous flow of changes and refreshes. I got to see the updates that were important to me in milliseconds, instead of minutes. V.cool.
Of course, with JavaRebel 2.0 right around the corner, it will be interesting to see what effect winning this award has on the release.
1) Does the JOLT award carry any value with it? Do you try a tool, because you see the award next to it on their site?
2) From JavaRebel customers, we’re hearing numbers like “JavaRebel saves 10-40 minutes, per developer, per day of development”. Since 2.0 has an easier setup, and covers more situations where redeploying is necessary, how can we share this information, without sounding too “marketingy”?
Special Note: Thanks to Shashank Tiwari for sending us email updates, and offering to give an acceptance speech for us last night! We really appreciate it!