Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Notation, and the 'business case' for Perl 6 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Perl6 almost certainly will dominate the professional software environment within a few years of the first practical implementation. The business case for using perl6 as the primary development language in a business or software house are as follows:
    1. Perl6 is inherently parallel. Junctions (and other innovative language contructs) offer programmers an intellectually easy method for writing programs with parallelism. Multiple cores already are required to increase computer performance, so languages that of

    • If [Perl 6] software is too slow, it will be impractical.

      That's too simplistic. Plenty of projects do just fine with languages and runtimes and environments considered "too slow" for other projects.

      A language without an IDE and visual debuggers cannot be considered modern or effective.

      That's too simplistic too, depending on your definition of "modern" and "effective". I never use the Perl 5 debugger and I wouldn't likely use it if I had an IDE with a visual debugger. I believe I can write very effective, modern Perl despite my stubbornness -- and I don't see how an IDE or a visual Perl 5 debugger would add much productivity.

      I do use a C debugger.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.