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.
I don't understand the article
by hmmm on Sun 17th Oct 2004 17:39 UTC

The parrot talks Perl 5 and Perl 6. Its even rumored that we will be able to use Perl 5 objects, modules and functions from within Perl 6 and the other way around. But the interesting stuff is how one might be able to use methods from C++, python or java code from within a Perl 5 or 6 script. As well as parrots cross-platform assembly style language.

I look forward to exploring all of this technology. I'd also like to learn ocaml, python, C, objective C, C++, C#, python and maybe java if its still around when I finally get the time to look at it.

Perl 6 adds a lot of features that I will find useful if I need that much organization and complexity in my code. But Perl 5 has everything I want right now. I'm just writing objects and simple methods to handle most of my stuff. I don't need complex methods that process data differently depending on how its called or what datatypes are passed to it and I don't need complex datatypes atm. In the future I'd love to have the power Perl 6 has to offer for when I might need it and I love the idea that I can make use of all this Perl 5 code I've been writing without rewriting it. What more could I ask for? Well, compiled binaries, but I'll deal with that later. Perl 6 is one step closer to native binaries, IMO.

But I guess that is why I feel the need to learn C and stuff.