I'm coming to this thread late, but I have a couple of observations.

I'm not sure what your thesis is. I'm an engineer, and my motto is, The right tool for the right job!

For me, Perl turns out to be the preferred tool for most of what I do on the job. Sometimes I *could* use Perl, but a shell script is just easier. The fact that it's lighter weight is a bonus.

Wanting to use an IDE is a developer preference. I loved Borland's Turbo C when it came out, about 20 years ago, and I used it professionally on DOS in the late 80's and early 90's. I moved to OS/2 and Presentation Manager after that, and went to an editor called KEdit. It had some IDE features like reading the error file and placing the cursor on the source file line with the syntax error.

These days gvim is enough of a development environment for me .. if I have a syntax error, I can find it as quickly as I need to, and if I need to look up a function, I'll just open an xterm window and look it up using perldoc -f split, or even open up my copy of the Camel.

I'm still not sure that good multi-threading is absolutely necessary -- I suspect that the number of problem domains that need this feature is small, and that this argument is a red herring.

The whole GUI thing is just a toy. I'm happiest on a command line, and I've been using a command line for 30 years. A GUI is fine when you want to do a limited number of things. It's very frustrating when you want to be creative. For example, recently I wanted to print a bunch of Java source files, two up. How the heck do you do that with a GUI? With the shell, I just did 

ls *.java | xargs -iyy 'mpage -2 yy | lpr'

[download]
and I was done. Yes, I had to read the man page for xargs -- I don't use it often enough -- but I knew it existed, and that it would do the right thing.

If you're talking about development of a GUI application, I'm not sure Perl is the best platform for that -- you probably want to think about using Java for the frontend, and Perl for the backend. That way you get the best of both worlds: A flexible GUI that's portable, and terrific power in the backend where you need it.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Re: Slow evolution of Perl = Perl is a closed Word by talexb
in thread Slow evolution of Perl = Perl is a closed Word by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.