From your post I've got a feeling that you're not TDD addict and that you're doing development directly on production server (or why else to bother about performance).
I think perhaps you misunderstood the OP.
TDD is great but when developing a web application you also need to test out your application in the browser as you develop. Relying completely on TDD for this type of thing is a recipe for disaster, you *always* need to do some real-world user testing as well.
Secondly, I highly doubt the OP is developing on the production server. I would suspect he is talking about developing on a local mod_perl enabled development server. His concerns about performance are valid since often times with mod_perl apps there is a lot being pre-loaded and startup can take a while. In cases like this a long startup delay can really slow down the development process, especially if the restart is unnecessary.
In reply to Re^2: A better way to see module changes in a running web server
by stvn
in thread A better way to see module changes in a running web server
by swartz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |