comment on

A good IDE, like Eclipse for Java.
Good multi-threading.
Standard and rich GUI.

These are very superficial reasons against a language. IDEs are a matter of personal choice. Multi-threading is being worked on, and is of limited use for web apps anyway (even on multi-core processors). GTK2 is pretty good for GUIs and works pretty well across platforms, with a few other choices beyond that.

If I was going to bother moving to a new primary language, it'd better offer something clearly superior to Perl. The kind of stuff that's been kicking around CS departments for a long time, but has barely registered in mainstream languages. Stuff like type inferencing or operators in RPN notation. If the language isn't going to challenge me to learn new concepts, it's hardly worth learning.

"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.

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

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks