Why install a second perl with its own module library?

I've learned much, which should be justification enough for any effort; nor do I think my education is finished. Primarily, I feel comfortable with this separation of church and state. I enjoy the rare feeling of actually going along with the majority opinion.

I get to experiment freely, even rashly, with the development environment without fearing to wake up to funny green squiggles marching across my screen. There's a limit to this, I guess, but a develenviron pushes that limit a bit further away.

Compiling locally is good preparation for building the production environment on remotehost. I have just about got comfortable with the idea of throwing out remotehost's perl 5.8.8 entirely and installing fresh to match localhost:/lab, thereby blowing away the version compatibility questions, the module version questions, and the cargo cult module loader prescribed for lesser mortals.

I've compiled my dev perl as 5.10.1, which beats Ubuntu's default install of 5.10.0; I've also now got threading and debugging support. I might could substitute my new, hot-rod perl for system use. It's also possible that I could try and end up with blue flames shooting from the vents.

On the gripping hand, my nice clean Ubuntu system works; and my nice new dev perl works.