in reply to Re: Perl: friend or foe ?
in thread Perl: friend or foe ?

Precisly,

Having to call up the heavy duty C code highlights the point of my question. The perl code is not quick or 'strong' enough to cope with the heavy duty tasks. WHY?

Im not sure if im jumping out on a limb, but, with Java, it easy to write the code, test, re-write, re-test, and release. The one disadvantage is that after re-writing it has to be compiled again, BUT, its quicker in the long run if a big application was running.

Feel free to spank me on this but, doesn't perl only cope with some much smaller tasks, i.e. something that does not demand a high level amount of processing. If this is so, WHY?

MonkPaul

Replies are listed 'Best First'.
Re^2: Perl: friend or foe ?
by merlyn (Sage) on Apr 24, 2005 at 14:12 UTC
      From what I've heard, Amazon is not pure Perl. While they use a lot of Perl, they use a lot of other stuff as well (eg Java).

      I've also heard that Ticketmaster is currently planning to move from Perl to an optimized C architecture. (We'll see if that actually happens though..)

      I have heard no recent rumors from IMDB, so I don't know their status.

      Good stuff,

      BUT, is perl used for such tasks as instrument interaction (lab equipment, or printer control), or some stand-alone package like a word processor or photo editor.

      I understand the above reply, but to me it seems as if they are web applications. Does this wide use still apply to desktop applications?

      My other question would be, why progress in creating a language has not turned to utilising the best from all other languages, like SQL database queries, C++ and Java object orientation, Perl text and mudule interaction etc. etc.

      Im still interested in other peolpes view so keep them coming.

        Re your second question, I would say that perl has a tendency to do exactly that. Not only in allowing one to inline code from other languages, but in adopting facilities from other languages as it develops between versions; overloading and extension by modules etc.

        Take for example PDL. It's still recognisably perl, but perl extended in a particular direction, adopting functionality from Matlab.

        The community developed/supported nature of perl means that, if someone sees a need for a particular facility, they will very often write it as a module. Class::HPLOO for example allows one to create OO classes in a manner rather more like java. DBD::LDAP offers a degree of SQL syntax interaction with LDAP.

        Perl has, IMHO, the biggest range of functionality of any programming language. A one liner can sometimes perform tasks that would require many lines in e.g. a shell script, and at the opposite end of the scale a fully functional GUI app can be written in perl. The fact that perl is so easy to use for quick and dirty fixup scripts perhaps leads people to underestimate the power and flexibility that it is capable of.

        Update: As far as heavy use goes, I use perl for neural nets, which involves a very large number of FP calculations. It's not as quick as C - it's reputed to be 20-30% slower. But it's a lot easier to dig around in the guts of the code, and runtime compilation means I can modify the code, and not have to wait half an hour for the app to build before using it.

        g0n, backpropagated monk