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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I tend to think of this along the lines of "making hard things easy and impossible things merely hard". With that in mind, the frontier has shifted since Perl was developing rapidly.

    My gut feeling is that the "wow" factor has become harder for Perl to achieve because what wows people isn't insanely great string, dataset and administrative task manipulation. People want to see results quickly. That's not just about the learning curve -- it's the end-to-end process.

    Part of the advantage of Java in an educa

    • On parallel processing:

      There's got to be a better way to do this.

      No dynamic language has found it yet. Even 2 full time Google engineers have failed to find it for Python [google.com]

      CPython has a Global Interpreter Lock, single threads the interpreter, and hence single threads compute intensive task. [C]Ruby has "green threads" (i.e. it does the thread scheduling). There's no prior art. There's no proof that the problem even has a solution.

      • As I noted above, Clojure is a dynamic language that provides a solution. There is prior art, it just doesn't look or feel like Perl/Python/Ruby.
        • Sorry, I wasn't clear enough. My fault. Prior art for a dynamic language implemented in C. Clojure is a dynamic programming language that targets the Java Virtual Machine. (To the best of my knowledge) Jython does threads just fine - it's CPython that can't, and even the folks at Google working on Unladen Swallow can't see how to take that Jython know-how and port it to the C implementation.

          • I don't think there's anything stopping Clojure from being implemented in C if they actually wanted it. The problem for CPython and Perl isn't that they're in C, but that the entire language is based on the idea of default mutability. Clojure was designed from the ground up with a different multicore-focused approach to state in mind, which is why it works. You'd have to fundamentally change Python and Perl as languages, no matter what their implementation, to get them to do handle threading well.