I see two lines of thought here. The first can be represented by:

"Perl doesn't have an infatuation with enforced privacy. It would prefer that you stayed out of its living room because you weren't invited, not because it has a shotgun."

Which means - since the source is open anyway there's no point in securing the code itself but rather the machine that runs it. That I am happy agree with. On the other hand, I also see this line of thought:

"The only way to secure your computer is to remove drives and weld the case."

This is something I once saw in a discussion about securing desktop PCs from tampering, where somebody commented that usernames and passwords are a waste because "I could always go to that PC and boot it with Knoppix". Yes, he could. If one is determined enough, he can crack into almost anything. Will that make anyone take less care of security? So the comments like "Java programmers just think their code cannot be decompiled" are a bit like saying "weld your case". If you have the time and patience, you can disassemble even a binary file and learn how it works. Most people (and the average script-kiddie) won't, though - at least that's what seems right to me.

Regarding inside-out objects - very nice. Reminds me of the old days, before OOP, where if your program had three veteran soldiers, you'll have 3 places in the num_limbs array, 3 places in the medals array, etc. That's doing OO without too much fancy OO syntax, but also without too much hassle.

PS - off topic: It's Yom Kippur here in Israel, a day that is devoted to contemplating our sins and mistakes in the now-ending jewish year, and a time of asking and giving forgiveness and making peace with each other. So - I sincerely apologize for any post that was too much off topic or too stupid, for posts where I said wrong things, etc.