use Perl

• What is scrottie code? (Score:1)

  by beppu (899)

  When I think of scrottie code, these are the characteristics that come to mind:

  • minimal (so that it can run on your old hardware)
  • concise (for its own sake)
  • unusual (...your penchant for coroutines and byte code manipulation comes to mind)

  When I think of Java code, I think it's:

  • bloated
  • wordy
  • normal (in the worst way possible)

  That's why I find it unusual that someone like you would find reasons to like Java. But if you like it, whatever.

  I know that you don't actually code in it that much
  • Re: (Score:1)

    by scrottie (4167)

    "I know that you don't actually code in it that much. ;-)"
    
    That's key. I can take lots of stuff in small doses, and enjoy it. Just not PHP.
    
    When writing Java, I used to use kaffe and jikes. Both are pretty small, and both are open source and support my old, slow hardware. jikes is extremely fast. kaffe only does 1.1ish or 1.2ish, but at the time you had to program down to that version anyway to support MS's fuxored Java version they distributed with IE. And then compared to Flash, which was barely progr
    • Re:What is scrottie code? (Score:2)

      by jdavidb (1361) on 2007.07.27 9:04 (#56543) Homepage Journal

      most Perl programmers would do well to spend some time ignoring the language itself and just concentrate on design.

      Hmm, I think of Perl programmers as actually focusing more on design than the Java I've seen. For a community that values TMTOWTDI, there sure is a lot of emphasis at times on making sure you do things the One True Best Way, which can be good for design. That's one reason I ask Perl programmers questions involving other languages.

      I, too, really like interfaces. :) Unfortunately the Java programmers I've dealt with never use them. :(

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers

      Reply to This

      Parent

      • Re: (Score:1)

        by scrottie (4167)

        Hi jdavidb,
        
        You make some good points.
        
        There is a movement in the Perl community towards clean code (Perl::Critic). We collectively seem to have fallen in love with MVC frameworks. In trying to do things the right way, we obsess over decisions like Mason or Template::Toolkit.
        
        But, compared to the Java camp, we don't read about OODA. (We also don't read about project management methodologies, which is a good thing, IMO.) Rather than going out and buying _Design Patterns_ and _Refactoring: The Art of Improvi