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.
Steven Haryanto
by Simba on Sun 17th Oct 2004 17:36 UTC

"There's module nesting, aliases, hooks, ObjectSpace, object "freezing, extending individual objects, protected/private/public as in C++ (Python doesn't have protected IIRC), etc."

Well, some would argue that "Protected" violates encapsulation. Of course, the flip side of this is that without Protected, folks usually result to making things Public rather then do the additional programming required for them to work as Private.

I don't know that much about Ruby, but does it support the functional programming aspects that you can do in Python? For example, does it have lambdas and generators?