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.
  • first there was notepad. and it was good.

    then there was vi, and it was better.

    then there was vim, which seriously pisses in vi's cheerios.

    I've even brought over a port of vim to my old MacOS 8.6 machine, I like it so much. Even stopped using BBEdit over there.

    Lately I've tested bluefish and quanta on Fedora Core 1 for web development and continually kept going back to gvim as I was just far more productive in it. EVEN given all these extras that come with those two. (I also tried screem but it's IMHO not ready for prime time yet)

    So, this client's site, which uses Perl (CGI.pm, DBI, DBD::mysql), PHP, MySQL, Javascript, HTML 4.01, CSS2, all beautifully woven together, was basically done entirely in vim. The syntax highlighting and auto-indenting are superior. macros, multi-windows, multiple clipboards, marks, comment-folding. Life is good. :o)
    • First there was ed, and it was THE STANDARD.

      Then there was vi, but it required grabbing a glass terminal, and who could manage that?

      Then there was emacs, which thrashed magnificently on underspecced timeshared Vaxen.

      But emacs grabbed the finger-control neurons, so must now be ported to any new platform before work can be accomplished.

      I still sometimes use ed for those "change one line" jobs.