Linked by Shlomi Fish on Sat 16th Oct 2004 07:28 UTC
General Development The purpose of this essay is to explain why I believe Perl 6, the way it currently seems to progress, is the wrong thing at the wrong time, and why I predict (with all the expected caveats of predicting something) that it won't be successful. I will also suggest a better alternative for the future of Perl which makes more sense at this point.
Permalink for comment
To read all comments associated with this story, please click here.
re: verbat
by Simba on Sun 17th Oct 2004 20:51 UTC

"almost always in java you can still access private stuff:"

With a standalone app, sure you can do this. But there are few guarantees when dealing with stand alone apps since I can just as easily write a trojan horse in Java that will read any file the user running it has access to, or delete every file in the user's My Documents directory, or something else malicious.

But where the most potential for dangerous content comes from, is dynamically loadable applications such as applets or Web Start applications. and with applets and Web Start, the security manager will not allow reflection by default.

Python's name mangling does prevent you from shooting yourself in the foot. But it doesn't prevent someone else from shooting you in the foot. There are various ways in Python to perform tasks similar in Python to what is done with Java. But in Python, there is no safe way to have a module from an untrusted source interact with your own modules.

In Java, however, if you are having an unstrusted class interact with your own classes, you will usually be using a security manager that will not allow thinugs such as reflection and such.