Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • by jmason (3282) on 2004.09.23 19:34 (#34646) Homepage
    I'm curious. You say "TIMTOWTDI is often viewed as being the antithesis [of] standards" (I presume you meant an "of" there). Is that the case? If I write two different object models, using good Patterns for both, haven't I implemented MTOWTDI using standards -- and possibly even done it well?

    Anyway, my beef with big "do it all for you" class frameworks is that:

    1. I haven't seen any compelling evidence that it produces better results, so far

    2. it insulates me too much from the iron, and when things go wrong, I *still* have to dig down into the lower levels to deal with that stuff, myself

    3. in a past life, I worked on a team *developing* an implementation of a "do it all for you" class framework -- CORBA in those days, and both we the developers, and our customers, ran into #1 and #2 repeatedly. ;)

    4. my experience working with big companies is that they haven't a clue what makes for good software development, so why should they dictate what OS/framework/development style/object-modelling strategy I should use?

    • I must say that I agree with all of your points. However, it's a matter of perception. Until we can convince those who actually make the language decisions that Perl is a good choice, they still are going to choose other languages. Let's face it, Java's market share is due to their marketing share and despite Perl programmer's protests to the contrary, there are sometimes very good reasons to choose Java over Perl.

      For a while I thought that those reasons would go away when Perl 6 comes out but I was fi

      • I'm not sure it's possible for me to care less if the CIO of a random Fortune 500 companies doesn't realize that design patterns are a lot more important to Java than Perl because Java's much less flexible than Perl. I wouldn't expect him to make smart decisions based on that knowledge anyway.

        I don't expect big companies to make smart decisions. I expect them to make "safe", top-down decisions that don't really have much bearing on the people who do actual work. Meanwhile, I expect a big chunk of the r

        • then I'd darned well care about any company that might potentially be convinced to hire me. Big, small, stupid, smart. A paycheck is a paycheck.

          Given the choice I'm with you, I want a smaller company that tries to evaluate languages and hire the right people. Working with the right people is so much more fun than the alternative.

          But I see where Ovid is coming from as well.