use Perl

• My case (Score:1)

  by colomon (8994)

  I've used Perl professionally since 1995 or so. I saw someone (Damian maybe?) give a presentation on Perl 6 back in 2004 (I think) and was instantly hooked -- it was just obviously better than Perl 5 on a number of issues important to me. So I'm pitching in to help get a Perl 6 compiler to the point where I can start using it everywhere I use Perl! But also, it is a great pleasure to work on a system with good tests and where small changes can accomplish useful things. My $work all too frequently invol
• what might be your case (Score:1)

  by gfldex (9543)

  A good physical analogy of programming languages are bridges. Getting over a river without getting wet can save your health (getting sick is pricy and ppl that use terms like business plan hate pricy). In bridge-terms providing Perl (awesome) 6 free of charge is like making tools to make bridges available to anybody who likes building bridges. Ofc, you could just build the bridge yourself and therefore could keep Perl (awesome) 6 all to yourself. But with the free as in beer thingy and a bit of time you mig
  • Re: (Score:1)

    by masak (6289)

    A good physical analogy of programming languages are bridges. Getting over a river without getting wet can save your health (getting sick is pricy and ppl that use terms like business plan hate pricy). In bridge-terms providing Perl (awesome) 6 free of charge is like making tools to make bridges available to anybody who likes building bridges. Ofc, you could just build the bridge yourself and therefore could keep Perl (awesome) 6 all to yourself. But with the free as in beer thingy and a bit of time you might end up being able to cross _all_ rivers because you give power to the (slightly strange) ppl.

    Hm. But I imagine bridge-building tools aren't free of charge, so I'm not sure if the analogy helps me. It tells me more about how building programs is not like building bridges...

    This explanation might suit your dad who is of cause worried about your financial situation.

    I'm going to read that as 'mindful of' rather than 'worried about', because the latter sounds like you know something about my financial situation (or my father) that I don't. :)

    And as many stories-for-parents it's complete and utter cow poo.

    Hm. That ('complete and utter cow poo') would be a step down from what I was aiming for: to put what I'm doing in terms that he can understand without dis
    • Re: (Score:1)

      by gfldex (9543)

      Hm. But I imagine bridge-building tools aren't free of charge, so I'm not sure if the analogy helps me. It tells me more about how building programs is not like building bridges...

      If we put the same amount of afford into bridge building tools then we did invest into information transportation tools (think of all the miners that minded all the copper that was used to make the cables that where needed to power the routers that make it possible that you can read my words right now) it might get possible to provide bridge building tools by everybody to everyone who is willing to play 15 EUR per month.

      I'm going to read that as 'mindful of' rather than 'worried about', because the latter sounds like you know something about my financial situation (or my father) that I don't. :)

      Do you have children of your own? If you do and you are not in the constant state of mil
  • Re: (Score:1)

    by Aristotle (5147)

    I would say that Perl 6 is itself a bridge.

    If you put a bridge across a river in the right place, even if that spot was previously deserted, you’ll suddenly get a lot of people passing through. And with them, you get opportunities – lots of different opportunities, small and big. You don’t know what they will be when you build the bridge, but they will happen.

    You are enabling serendipity.

    In some sense Perl 6 is a classic Microsoft strategy – it’s a platform play.
• uuh ? (Score:1)

  by thickas (5805)

  Perhaps I am even more retarded than usual, but I think mazak senior's question was perfectly reasonable and the meta-answer pretty obvious.

  The 'business case' for something is a demonstration than spending whatever it costs to do something, is less than the 'benefit' gained by doing it. It usually quantifies costs and benefits in $ terms since most decision makers are responsible for the cost of their activities and just about anyone understands partial orders in the cash domain.

  The business case for Per
  • Re: (Score:1)

    by thickas (5805)

    tsk tsk ! s/mazak/masak/g ; sorry

    Notational superiority is a quantifiable benefit. As well as your excellent examples, you could also add that adequate expression of a problem is an important step in both understanding the problem and solving it (see http://en.wikipedia.org/wiki/How_to_Solve_It [wikipedia.org]).

    Cheers !
• More is better, less is more. (Score:1)

  by finanalyst (9378)

  Perl6 almost certainly will dominate the professional software environment within a few years of the first practical implementation. The business case for using perl6 as the primary development language in a business or software house are as follows:

  1. Perl6 is inherently parallel. Junctions (and other innovative language contructs) offer programmers an intellectually easy method for writing programs with parallelism. Multiple cores already are required to increase computer performance, so languages that of
  • Re: (Score:1)

    by chromatic (983)

    If [Perl 6] software is too slow, it will be impractical.

    That's too simplistic. Plenty of projects do just fine with languages and runtimes and environments considered "too slow" for other projects.

    A language without an IDE and visual debuggers cannot be considered modern or effective.

    That's too simplistic too, depending on your definition of "modern" and "effective". I never use the Perl 5 debugger and I wouldn't likely use it if I had an IDE with a visual debugger. I believe I can write very effect