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.
  • Imho the problem with EcmaScript (and its JavaScript deviant variants) is not so much that it's a bad language -- it has limits and faults, but so do all the other ones -- but more that it's a language that was taken over by people that know nothing of programming (and that's not taking into account differing implementations if you're coding for the web at large).

    I've developed a rather large (several thousand lines) EcmaScript app for a thin-client (using SVG of course) with little prior EcmaScript knowledge and I must say that it was a rather pleasant experience. Of course, I was writing a codebase from scratch and I was relying only on sane implementations (ie the Mozilla engine for 1.5, which is also what is present in Adobe's SVG viewer). ES has cool things such as a type system that allows you to simulate what it misses most (especially classes/namespaces), Perl compatible regexen, built-in exceptions, and quite a few other neat things. Coupling that with the amazing flexibility of the SVG viewer, I don't think I ever built a GUI that communicated with a server using XML messages so fast. I don't use it much these days, but I am certainly looking forward to ES 2.0.

    --

    -- Robin Berjon [berjon.com]