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.
  • Why, exactly, would one want to use just the one language... I'm quite certain that the best mini language for user-interface generation isn't the same as the best language for user-scripting, and isn't the best language for back-office transaction processing.

    Now, the best glue between each of them...

    • That's a good point. Web interfaces aren't moving away from HTML/XML/CSS/etc. any time soon. You could call that a language if you wanted -- especially compared to some of the alternatives (e.g. writing UIs in Java against SWT.)

      But when you look at the structure of the AJAX model, you've got some XML munging at the server, and some XML (for all practical purposes) munging on the client. The server is typically written in Perl, Python, PHP, Ruby, Java, C#, or Befunge, and the interactive bits on the cli

      • JavaScript is probably a whole lot better for XML munging than most other choices, assuming that E4X [ecma-international.org] actually gets deployed in any sensible fashion. As usual, it's a lot easier to deploy to a server.

        -Dom