> I need to compile the whole thing if I have to make even a tiny change. How is "compile if I need to make a tiny change" affecting deployment? Use Play. Or u

> I need to compile the whole thing if I have to make even a tiny change. How is "compile if I need to make a tiny change" affecting deployment? Use Play. Or use other hot code reload options for dev. As for deployment: > Therefore, deployment becomes an event. Events tend to be planned and managed, hence slower. Deployments are events, and they tend to be planned and managed. 1. Check all tests are green(deployment tool can auto-check it). 2. Tag source. 3. fab deploy(or whatever) 4. Do some user level smoke testing that everything worked. In case of Java, compiling a jar isn't that big an addition to the list. And seriously, it's not like you compile manually when you have to deploy. You set up `ant deploy` or equivalent which will run tests, jar it, tag it, push it, restart server if needed. Deployment isn't different from what you do in Ruby or Python.