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.
  • The situation with Java comes down to one thing. Protection before execution.

    Java has a simple structure, it's easy to parse. So the editors and toolchain can be made SO much more rich for Java than for Perl.

    Then do extra checks at compile time, that we can't do.

    They have the equivalent of strict and warnings on by default.

    All of these checks are aimed at weeding out evil as early as possible, and managing it when it happens (exceptions).

    Of course you can write evil at the level above where the toolchain ca
    • The situation with Java comes down to one thing. Protection before execution.

      Don't forget lackluster abstraction possibilities, a huge standard library, the mad rush to standardize on One Giant API To Do Things, and programming, configuration, and deployment mechanisms that emphasize Lots of Little Fiddly Bits .

      The amount of damage you can do has some correlation to the amount of productivity you can achieve.

      (There's probably a more profound point related to the idea that there are very few system

      • Don't forget lackluster abstraction possibilities, a huge standard library, the mad rush to standardize on One Giant API To Do Things, and programming, configuration, and deployment mechanisms that emphasize Lots of Little Fiddly Bits.

        The key isn't to live in what Brian Eno would call the "small here" or the "short now". Computing is an evolving story, and what we've seen so far is just the opening chapters.

        If you look back 20 years, microcomputers were a stifling platform, because of their anemic

        • > Another way to look at it is that Java is solving a problem
          > of managers who would rather reduce risk at the expense of
          > increased power and productivity.

          That's a very negative way of looking at the problem.

          One thing managers are used working with that we aren't so much is the element of Trust as a malleable entity.

          When you work alone, or in small teams, you can learn a lot about people, and trust isn't a big issue.

          When you have big teams of people, or work with dozens of outsources, then you simply don't have TIME to trust everyone, or sometimes anyone.

          You can't instinctively trust the people you are hiring, the people you contract with, your boss, anyone really.

          And I suspect that managers get attracted to systems that allow them to deletegate and manage work effectively WITHOUT having to trust them. And the number of entities that are able to trust is finite.

          So if you trust Sun + Java, and Sun provides all these protections so you don't HAVE to trust the coders you are hiring 10 at a time, that's totally great!

          You might trust Perl the language, but Perl except for tainting Perl doesn't provide many tools that let you not have to trust your coders. Hence the problem in environments where you want to hire lots of coders...
          • That's a very negative way of looking at the problem.

            Not at all. It's the engineer's lament that the best solution frequently doesn't win. This is just a case where superior technology (e.g. Perl) is loses out to an inferior technology (e.g. Java).

            Trust is a significant part of the social issue here, and it's not something that open source can generally solve on its own. Linux and MySQL are thriving in large part because of the corporate umbrella provided by RedHat (et. al.) and MySQL AB that ma