Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Slashdot: next gen Python vs. Perl 6

by ww (Archbishop)
on Feb 01, 2008 at 19:53 UTC ( #665631=perlnews: print w/replies, xml ) Need Help??

Interesting -- at least for the early defense of Perl6 -- discussion underway at slashdot

Also noted: initial post is re the next iteration of Python... but it's tagged with "perl."

...and yes, one could argue the thread for this could be Perl News, except for the lack of Perl news.

Replies are listed 'Best First'.
Re: Slashdot: next gen Python vs. Perl 6
by ForgotPasswordAgain (Priest) on Feb 02, 2008 at 05:30 UTC
    One of the comments said something like "without pruning, Python would eventually turn into Perl with mandatory indentation", which seemed to imply that languages necessarily need to change in backward incompatible ways. We've obviously got Perl6 coming, too, and probably Ruby will eventually just to not be left out. But there are languages like C that don't seem to require that kind of radical change despite having been around for a long time. Is it a matter of scripting language versus real language, or am I just beating a dead straw herring?
      But there are languages like C that don't seem to require that kind of radical change despite having been around for a long time.

      C doesn't require much change because it reached its main goal of spreading a slightly less ugly version of PDP assembly code to other processors a long time ago. The language has low ambitions.

Re: Slashdot: next gen Python vs. Perl 6
by webfiend (Vicar) on Feb 03, 2008 at 11:05 UTC

    Oh man, those Slashdot threads irk me more than they should.

    Python has never been morally opposed to breaking backwards compatibility. We went through this in the 1.x - 2.0 shift. Heck, this time around the Python developers are being rather charitable. There will be a 2.6 release around the same time as 3.0 final, and the 2.x line will continue for a while. Tools are being provided to make the minimal changes needed to allow crufty old code to work in the shiny new interpreter. And large organizations with a huge pile of legacy code probably won't be leaping on 3.0 the day it's released.

    Some folks have been shouting about loss of backwards compatibility with the looming-ever-closer Perl 6 release despite frequent reassurances that legacy code will be covered one way or another. It doesn't look like 5.x is going to be going away any time soon. And again - despite how cool Perl 6 looks, it's going to be a foolish company that decides to convert all of their existing code to P6 on the day after Christmas.

    Major version number changes are the perfect time to change your mind about how a language should be used.

      Oh man, those Slashdot threads irk me more than they should.
      Especially when they make a big deal out of horribly old news.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (6)
As of 2022-06-28 12:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My most frequent journeys are powered by:









    Results (90 votes). Check out past polls.

    Notices?