Slashdot Mirror


State of the Onion 9

chromatic writes "Perl.com has just published Larry Wall's Ninth Annual State of the Onion address from OSCON 2005. In previous talks, he's used screensavers, music, and Unicode to explore Perl and open source. This year, he introduced the cast of characters in the Perl community in terms of spy movies and metaphors."

9 of 174 comments (clear)

  1. Re:What I've learned from Pugs. by slavemowgli · · Score: 4, Informative

    Functional programming has been around for a long, long time, actually, but it has never revolutionised programming, so I'm not sure why Haskell should do it now - it's been around for almost 20 years already, too.

    Not that functional languages don't have their merits, of course, but I honestly don't see why they should suddenly take over and obsolete other programming paradigms now.

    That being said, have you taken a look at Curry? It's a language that combines functional and logical programming (à la Prolog) - definitely rather cool.

    --
    quidquid latine dictum sit altum videtur.
  2. Re:Screensavers, music, and Unicode? by lullabud · · Score: 5, Informative
    From my understanding of the situation, it's not his position to be finishing Perl 6, it's the communities.
    "Perl 5 was my rewrite of Perl. I want Perl 6 to be the community's rewrite of Perl and of the community."
    --Larry Wall, State of the Onion speech, TPC4
  3. Re:Of course functional programming is ancient. by slavemowgli · · Score: 4, Informative

    Oh, I didn't mean to imply that you said that Haskell was the first functional language - certainly not. I merely wanted to point out that Haskell isn't new, so if a revolution hasn't happened yet, why should it happen now?

    I've met many people, especially at the university, who believed that functional languages were the holy grail of programming and that they would be taking over the (computer) world Real Soon Now(tm). But it's never happened, and nowadays, I believe that these people are just out of touch with reality.

    Let's face it - the IT industry is just like any other industry, especially in one regard: things usually happen by evolution rather than revolution. Traits of functional programming languages will certainly find their way into the "mainstream" (and the "mainstream" languages), but nobody'll decide to just throw out all existing code all of a sudden and reinvent everything from the ground up in a new language - no matter how good that language is or, more important, how much better it is than the existing languages. Even object-oriented programming is really an extension of the imperative programming paradigm, not a replacement.

    Paradigm shifts do occur, but they occur over time, and it's a smooth transition, not an abrupt one. Statements like "we've hit the limits of imperative languages" may sound cool, but they ultimately don't mean anything - the limits are changing. Boundaries *can* be pushed, and *that* is something that is *especially* true in the computer industry in general and the software industry in particular.

    I won't deny that I'm not a fan of functional programming languages myself, of course. Personally, I think they're rather unnatural; it may be easier to model their semantics mathematically (and the mathematical models will be more "natural", too), but I also think that the step-by-step approach of imperative languages is more natural for the human mind - it's how we do things, and that's probably why imperative languages took off when functional languages didn't (and for the record, both functional and imperative programming language started at the same time, in the mid-50s, and the theoretical foundations, in the form of Turing machines and lambda calculus, also popped up at about the same time).

    Nevertheless, I do realise that functional programming languages have some very interesting and useful features, and I'm certain that these will be incorporated into existing languages (or new languages based on existing ones, in the sense that Java is a new language based on C, for example) eventually - and that's a good thing. Pure functional programming, however, will (IMO!) always remain a specialised niche for certain, mostly mathematical (that is, theoretical) problems that naturally lend themselves to being modelled in functional ways.

    --
    quidquid latine dictum sit altum videtur.
  4. Unless... by sootman · · Score: 2, Informative

    ...he can top "Perl6 will give you the big knob," I see no reason to tune in. :-)

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  5. Re:Perl 6 is a mistake. by moof1138 · · Score: 2, Informative

    Your post seems oddly familiar...

    Perl 6 is a mistake

    Perl 6 is a mistake

    Perl 6 is a mistake

    This is really getting to be a bit tiresome.

    BTW, moderators, please stop modding this troll up over and over every time Perl comes up.

    --

    Hyperbole is the worst thing ever.
  6. FP strikes back by SolitaryMan · · Score: 2, Informative

    I honestly don't see why they should suddenly take over and obsolete other programming

    I'm not sure about "obsolete" thing, but functional programming strikes back -- that is for sure. Why I say that? First, because I've learned from pugs the same thing: Haskell is powerfull. And there are many other guys, so haskell bacame more popular, thanks to Pugs and Autrijus Tang, its leading developer. Second, new programming languages are adopting functional features: map, reduce, lambda in python for instance. There will be many of them in Perl6. Then Sun is developing new programming language Fortress, which is rather functional too. Why haskell? Haskell is pure and with age of parallel and grid computing at hand this is very important feature!

    --
    May Peace Prevail On Earth
  7. Re:Screensavers, music, and Unicode? by Argon · · Score: 2, Informative

    > Wrote a program in Python yesterday? It's outdated, they no
    > longer use that function, you gotta re-code it. Should you do
    > it today? Nahhh, it's nearly five o'clock, better wait for
    > tomorrow's edition of Python so we get a whole day's use out
    > of it.

    What are you talking about? Can you name any changes that required you re-code your python program? Python major versions have fairly regular and introduce some major features (type unification, generators, decorators etc) but I can't imagine any thing that broke older python programs. Most of my old python 1.5.2 still run without any issues.

  8. Re:Ridiculous by MadAhab · · Score: 2, Informative
    Actually, backwards compatiblity with Perl 5 is a key design feature. But looking at how Perl6 handles class members, accessors, methods, arguments, overloading, inheritance, etc, etc, it's clear that there's a lot to be excited about. It just makes programming easier and more powerful, without (like Java) swallowing the OO koolaid so uncritically that simple things are made hard because "classes good, operators bad".

    Python is a nice language, but it suffers actively from design features that simply try to be unlike Perl - strip the "line noise" out, force tab indenting and what do you get? Opaque variables, hungarian notation, inconvenient editing, programming in widescreen. Whatever.

    --
    Expanding a vast wasteland since 1996.
  9. Re:Screensavers, music, and Unicode? by Hosiah · · Score: 2, Informative
    I can't imagine any thing that broke older python programs.

    Well, Blender scripts (specifically anything calling the math module) no go on 2.4, go on 2.3. To name *one* example. And what about the string/character-handling functions? Going through the docs, every other one of them has "Do not use, we're getting rid of this one." stamped all over it. Whole language has been that way since I got into it, where have you been?