Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
# A good IDE, like Eclipse for Java.
An IDE like Eclipse, which relies on static analysis is never going to be good enough for a language as dynamically typed as perl. Perl is just not that kind of language. The syntax is a relatively minor issue (and that's probably saying something).

The only reason it works on Java at all, is because Java seems to be designed from the ground up to have the programmer make extra-double-carefully clear what (s)he expects some object to be and do anywhere that object is used (or even just glanced at).

# Good multi-threading.
Perl's multi-threading is still under development. IMO it's mostly useful because it enables you to use native multi-threaded libraries. I agree it can be a pain to use, though. In any case, threads aren't needed to build GUIs. You can build a perfectly good GUI system using just callbacks/events for instance.
# Standard and rich GUI.
Show me one portable language that has a good modern looking, standard GUI. Tcl/Tk, maybe. Java definitely does not have one. Note that even Eclipse does not use the "Standard and rich" Java GUI, because it's too damn slow and ugly.


In reply to Re: Slow evolution of Perl = Perl is a closed Word by Joost
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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others admiring the Monastery: (3)
As of 2024-03-19 07:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found