Still, putting it in own namespace doesn't matter much, you could still be able to access other namespaces, right? So it still isn't shared hosting safe.
Alto when I think about it, it wont be able to mess with anything else's, than what is already yours.
If mod_perl2 is usable for shared hostings, than great! But is it suitable for them considering other things (memory usage for instance)?
Still mod_perl requires from you to be a good programmer, and even if it would be shared hosting safe, it wouldn't be for the "masses".
Alto that way, we (we - as somewhat good programmers :) could write applications for a mass usage on shared hosting - which would be better than where we are now.
And "masses" couldn't brake anything even if they try writing some bad code, right?
Comment on Re^4: More than mod_cgi less than mod_perl.
I think this version of mod_perl does address the shared hosting issue. The page I read (which I can't find right now) compared it to PHP's safe mode and also said it was a replacement for suexec. By changing the MPM, you can still offer all the power that the current mod_perl allows. I don't know anything about performance for either version.