A Perl 6 status update
Posted Dec 31, 2007 21:55 UTC (Mon) by dskoll
In reply to: A Perl 6 status update
Parent article: A Perl 6 status update
The creator of the project gets to name it, and he's happy with the difference being the version number.
Well, good for the creator, but bad for the rest of us. Having to completely-different languages given the same name is going to cause harm. For example: We ship a large commercial project written mostly in Perl 5. When (if?) Perl 6 is ever released, we have two unpalatable choices:
- Waste time porting our software to Perl 6 and making sure it runs correctly. I call this a waste of time because it is! Our software runs fine on Perl 5.
- Take endless support calls from confused customers who wonder why their version of Perl won't run our software.
If Perl 6 were called something else (I dunno, maybe Parrotugs or something) there'd be no problem. Our software requires Perl. If you also want to use Parrotugs for something else, great!
I'm also the maintainer of a couple of CPAN modules (MIME::Tools being the most prominent) and if Perl 6 were called something else, I wouldn't have to port MIME::Tools (which is after all a Perl module.) As it is now, if I want to maintain the module, I'm going to owe it to the audience to port it to Perl 6. This is work I don't really need, thanks!
All in all, Perl 6 really looks to me like a failed IT project. Lots of vapour, people running in lots of different directions, and very little actual working code. It frankly scares me.
to post comments)