Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Re^2: disadvantages of perl

by GrandFather (Cardinal)
on Jul 02, 2009 at 21:07 UTC ( #776851=note: print w/ replies, xml ) Need Help??


in reply to Re: disadvantages of perl
in thread disadvantages of perl

1) I'm not sure what you call a "real" application, but I've written a number of significant applications using Perl and Tk that are used daily by a number of people or are major parts of our corporate software deployment process. They look awful (Tk's like that), but were quick to write, are easy to maintain and are very appropriate to their purpose. Oh, and they are all running on Windows of course.

There is no "perfect" language, although there are languages that are well suited to particular application domains. Perl is a very good text processing and prototyping language. It is not such a good general GUI application development language, although it performs really well in that role for small applications if you don't care much about the "look". Perl can be very portable across systems.


True laziness is hard work


Comment on Re^2: disadvantages of perl
Re^3: disadvantages of perl
by elTriberium (Friar) on Jul 02, 2009 at 22:19 UTC

    I don't doubt that it can be a good approach to develop certain applications for Windows in Perl.

    It's more like a question I'm asking myself why I never got in contact with Perl when using Windows. All of the applications I use on Windows are either binaries (probably written in C, C++, C#, ...) or java-based.

    On the other hand on Linux I often see tools written in Perl. Most of them run on the shell and don't provide a GUI. So maybe that's the main reason here: GUI development isn't that easy / good / advanced in Perl.

    Don't get me wrong: I'm not stating that developing Perl on Windows is bad, I'd more like to state my own experience and maybe get some input from others to understand if I have some misconceptions there.

      Web apps are GUIs and with a huge amount of well defined cross-app behaviors which add value and guarantee some level of user acceptance/experience. Some of the best/biggest apps in the world are all/mostly Perl.

        That's true and a good point. But then still the question remains "why are there so few non-web-based Perl apps for Windows compared to Linux?". My own explanation is that a) Perl isn't pre-installed on Windows an b) Windows applications are usually GUI-based which isn't Perl's strongest feature.

      I do GUI Perl programming for Windows, using Win32::GUI. It's not exactly easy, but it's not too bad either; most problems can be solved given sufficient STFW time. I do sometimes feel that the time spent solving GUI problems is chewing up the time saved by going to CPAN for the core logic, though, which would be my number one complaint about Perl.

      Number two complaint -- threading. I have to write sequentially, because forking uses so much memory and threading just doesn't.

      "Nothing was broken, and it's been fixed." -- Jon Carroll

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://776851]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (11)
As of 2014-07-30 10:17 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (230 votes), past polls