Slashdot Mirror


Perl And Standards: Larry Rosler Interview

Kaufmann writes: "In this interview with Joe Johnston (on O'Reilly's Perl.com), Larry Rosler (of HP, one of the people who helped put the 'ANSI' in 'ANSI C') shares his thoughts and advice on the value of standards, optimising Perl code, how Sun should handle Java, and programming in general. Will we ever see a Perl Language Subcommittee too?"

33 of 74 comments (clear)

  1. Re:Perl Standards by pornking · · Score: 5

    The OO paradigm promised to save the world of software engineering from bugs, complexity, and maintenance difficulties, but if the last 5 or 6 years are to be considered as indicators for future performance, it's not worth the hype.

    Think of it in terms of economics. People will write the most complex and featureful software they can that stays within the level of buggyness they can tolerate. Therefore, buggyness will tend to stay constant.

    Software is just as buggy now as it was 5 or 6 years ago, but is far more complex. I have personal experience with what can be done with OO to facilitate large complex systems which would be unthinkable without it.

    Therefore, people have taken advantage of the ability of OO to manage complexity and pushed the envelope with it. I don't consider this a bad thing.

    In addition, while I know Perl well and like it a lot, I would not dare use it for a large complex project.

    --
    pornking
  2. Why Perl would benefit from a standard by GGardner · · Score: 5

    According to this a group of hardy hackers are hard at work on a complete, from scratch, re-implementation of perl in C++. This reimplementation is supposed to be completely compatible with perl5. How can you guarantee compatibility without a specification? My guess is, in the same way that perl5 broke some obscure perl4 scripts, perl6 will break perl5 scripts - but without a spec, it's impossible to tell which of those breakages are bugs and which are features!

    1. Re:Why Perl would benefit from a standard by Chip+Salzenberg · · Score: 2
      Yes, I'm quite concerned about the possibility, nay, inevitability of Perl 6 breaking Perl 5 code. A standard would be helpful. But a standard would take too long to draft to help with the 5->6 transition, unless it were begun now.

      Volunteers?

    2. Re:Why Perl would benefit from a standard by JordanH · · Score: 2
      • Yes, I'm quite concerned about the possibility, nay, inevitability of Perl 6 breaking Perl 5 code.

      Well, it seems like your group would be best placed to provide material and consultation for this standard's work.

      You have developed some kind of syntax diagrams or parsing tables or something for your work, haven't you?

      When you say you are concerned with breaking Perl 5 code, does that include modules interfaced with XS? If not, I'm very concerned that there will be a danger of fracturing the Perl community, with people dependent on Modules that only work with Perl 5 and those who move to Perl 6.


      -Jordan Henderson

    3. Re:Why Perl would benefit from a standard by Animats · · Score: 2

      Even a formal description of the syntax would be a big help. "You can leave out ... if it doesn't matter" isn't enough.

  3. Re:ActiveState--good for Perl... or not? by pudge · · Score: 2
    The Perl Power Contest (sponsored by ActiveState) requires the use of ActivePerl, rather than encouraging generic Perl solutions

    This is incorrect. As reported on use Perl :-) you can use standard perl 5.6.0 if ActivePerl is unavailable for your platform. I guess that means that if you use Linux for x86, you need to use ActivePerl; but who is gonna know if you don't, and just use perl 5.6.0? They are the same thing.

  4. Garsh, I'm on slashdot! by jjohn · · Score: 2

    Well, I'm glad the interview was thought provoking, even if people don't agree with Larry.
    He seems like a smart cookie with Perl's best interests at heart.

    Hey, they have standards committees for a reason, I guess.

    I have to think P5P will not like this thread of conversation. :-)

    1. Re:Garsh, I'm on slashdot! by pudge · · Score: 2

      Yeah, but use Perl had this story before Slashdot did!

  5. Perl & VB by Anonymous Coward · · Score: 5
    >>Perl is superior to Visual Basic in every way imaginable.

    This is a completely stupid overgeneralization. VB is great at rapid prototyping of visual apps, and Perl sucks big at it.

    1. Re:Perl & VB by ajs · · Score: 2

      Nope. Glade does a great job of this. It's no Visual Basic GUI layout tool, but Perl does *not* suck in this respect.

      In fact, I can design a UI and do my prototyping using Perl, but because the GUI is managed by Glade as XML files, I can then move over to C, C++, ADA or guile fairly easily. I still have to re-write my code, but all the UI gunk is language independant. This means that you can hire UI people who don't even know the language you are writing your core system in!

      The next tool that we need is a program that makes tying your UI to your back-end through CORBA simple. It will have to be as simple to use as glade (perhaps even a glade plugin). Then we can have applications where the two are developed in different languages and stay that way....

  6. All the details I have... by tilly · · Score: 2

    Right here.

    It really is a nice construct though. I am a big fan of anonymous functions. For instance you need to emit errors from a module that will be used various places for various things. Have a package variable with an error sub, by default "croak" but overrideable. That is fine for development and interactive scripts. Now if someone wants to use that in a cron, they can replace your croaks with a routine to page someone before dying...

    Cheers,
    Ben

    --
    My usual seat in the cluetrain is at A HREF="http://pub4.ezboard.com/biwethey.ht
  7. ActiveState--good for Perl... or not? by the+way · · Score: 3
    Q: My understanding is that Microsoft is 'embracing' ActiveState's Perl. They will be shipping Perl with their "Services for UNIX 2.0". Do you see any chance for Perl to compete on a Windows Platform as a replacement for Visual Basic? In particular, as application "glue"?

    LR: Why not? Perl is superior to Visual Basic in every way imaginable.

    Maybe a push from Microsoft will help overcome the barrier of acceptability that I focused on above.

    ActiveState's support of Perl has been increasingly bothering me other the last 12 months... am I just being paranoid?

    ActiveState's work in bringing Perl to Win32, and supporting OLE effectively, has been a very important piece of work (and done very well to). But having achieved that, they now seem to moving towards the embrace, extend, extinguish paradigm that some might have noticed from a certain other company.

    For instance:
    • Packages are distributed in PPM format, which as far as I can see are quite separated from the CPAN model which has been so effective for the Perl community
    • The Perl Power Contest (sponsored by ActiveState) requires the use of ActivePerl, rather than encouraging generic Perl solutions
    • With Gurusamy Sarathy (of ActiveState) looking after the Perl 5.6 release (and doing a great job, I might add), the 'official' binaries for both Win32 and Linux are now ActivePerl packages
    • They are partnering with M$oft in many projects. This just makes me uneasy, given M$'s history.
    I don't mean to put down the many good things ActiveState has done... But I do feel that the Perl community should be a little cautious about being pulled along by them. Other than the flexibility and power of the language, the things I most like about Perl are:
    • Scripts I write will run on almost any platform I come across, as long as I avoid direct system calls and avoid assumptions about file system structure
    • I know that if a problem has been tackled in Perl, it's solution will be available on CPAN. And furthermore, I know that I can use the CPAN module to install it with just one command.
    It seems to me that it would be all too easy to lose these benefits if the MS/ActiveState version of Perl forks much more from 'normal' Perl, and if ActiveState develops its own community around PPM rather than using CPAN.
    1. Re:ActiveState--good for Perl... or not? by Imperator · · Score: 3
      Packages are distributed in PPM format, which as far as I can see are quite separated from the CPAN model which has been so effective for the Perl community
      AFAIK CPAN still works for non-Win32 OSs, and there are no plans to close it. PPM is necessary for Win32 because CPAN packages come uncompiled. That's a problem on Win32, where most users don't have a compiler, never mind a POSIX environment.

      Personally, I don't lose too much sleep over ActiveState. The Perl community has always been very vocal and pro-Unix. If ActiveState wants to provide and support Perl binaries, more power to them. Though they employ several Perl developers, if they were to fork, they wouldn't be able to maintain the huge beast without the support of the community, and p5p would happily leave them behind.

      Microsoft is interested in Perl for several reasons:

      • VB sucks, and they know it. It may be easy to write code, but serious programmers don't like it. (Microsoft, which employs a surprisingly large number of programmers, is acutely aware of this.) Microsoft wants to position Perl as a supplement for VB. They could integrate it with IE if/when Mozilla does the same. They won't do this until they need to, because VB is a great way of getting people to create web sites that only work with IE, but they don't want to be caught off-guard when people start scripting sites in Perl and thus requiring Mozilla.
      • There are a large number of COTS and free software CGI scripts written in Perl. Many IIS sites would benefit from them. (They already do, but more Win32:: modules wouldn't hurt.)
      • Microsoft always wants more people coding in a language that works on their OSs. Not having Perl on Win32 would really hurt them for this reason.
      If Microsoft ever really wanted to EEE Perl, they wouldn't be subtle about it. They could easily buy ActiveState. But it really isn't worth it to them: Perl has a strong community organized around a single open source interpreter, and very few people are writing cross-platform applications with a scripting language. (They were afraid of Java not only for this reason, but also because it was tied to Sun.) Perl isn't a threat to Microsoft.
      --

      Gates' Law: Every 18 months, the speed of software halves.
  8. Re:Perl Standards by JoeWalsh · · Score: 2

    Don't use one hammer but educate yourself to be able to use the appropriate tools for the job at hand.

    I agree entirely. Each language and, indeed, programming methodology, was created with a particular problem space in mind. Using each for what it does best is not a bad idea. I've programmed in BASIC (remember when it was an acronym, and needed to be capitalized?), assembler, C, Java, and a host of smaller, niche languages. Each did its job well enough.

    In my previous post, I wasn't saying that I've never used OO. I was simply saying that I never encountered the problem space for which OO is the most correct solution. I'd begun to doubt the existence of that problem space, and this interview helped me to realize that I wasn't the only one. I'd thought I wasn't seeing this huge elephant that the rest of the world sees standing right in front of me. But, apparently, either I'm not the only blind one, or the elephant isn't as large as it's been made out to be.

    -Joe

  9. Isn't perl already standardized? by Xerithane · · Score: 3

    I could see if there was GPerl, and SunPerl and IBMPerl, and HPPerl.. but there really is only one person so isn't that the standard?
    Hmm.. oh well. If it makes people stop using system calls in perl scrips I'll be happy.. I especially like the 'script' ne 'program' part. Jon++
    And why the hell are the first 5-10 posts always flamebait/trolls/offtopic?


    nerdfarm.org

    --
    Dacels Jewelers can't be trusted.
  10. Larry Rosler understands niche languages - kudos! by noahbagels · · Score: 2

    Rosler is not an object oriented trailblazer, nor is he out to prevent good innovation. Instead, he supports good languages that help do useful things.

    I've worked on massive multi-platform efforts at Oracle, and have to say that C is a great language for this. It is extremely compatible across platforms.

    Perl, although supporting some object behaviour, is capable of anything Rosler has needed from it. He (and many others) don't need heirarchy to write a simple web app, nor to format / translate data.

    Already, Perl has helped solve many simple development issues where I have worked. Although there is a cutting edge of enhanced Perl, the current 5.xxx library is quite mature. For tasks that don't require threading etc... simply use the tried and true Perl.

    just my 5x10^10 rubles

  11. No need to standardize by DA_MAN_DA_MYTH · · Score: 4
    I like the fact that a lot of people don't know perl, We don't need to make perl widely accepted...

    COME ON PEOPLE WE NEED TO KEEP THINKING JOB SECURITY!!!

    I also think it's funny that Visual Perl is coming out... Who wants to bet it will be called VP++ because of all the M$^%t add ons, doesn't anyone remember what happened with VJ++? Jscript was the only microsoft clone of a language that actually provides cool functionality.

    True, we are all gonna die...

    --
    "It takes many nails to build a crib, but one screw to fill it."
    1. Re:No need to standardize by lbrlove · · Score: 3

      That brings up a great point. I remember seeing the announcement of Visual Studio 7 incorporating Perl as a module at ActiveState. It looks like Microsoft is merely "allowing" this to be incorporated, and ActiveState is doing the work of building what amounts to a large plug-in.

      I wonder if this just entails the things that facilitate using the IDE (e.g. syntax highlighting, debugging, etc.), or proprietary code modules ala MFC (Microsoft Fried Chicken?). I further wonder if the guts of this big Visual Studio plug-in will themselves be open-source, or will they be grabbed by Microsoft. The arrangement is not terrifically clear if you just read the press release.

      Does anybody know the end game here?

      -L

    2. Re:No need to standardize by QBasic_Dude · · Score: 3

      The press release is here. ActiveState joined Microsoft's Visual Studio Integration Program. Visual Studio will contain a full-featured VB/VC++-like IDE. Visual Python will also be included.

    3. Re:No need to standardize by arivanov · · Score: 2
      COME ON PEOPLE WE NEED TO KEEP THINKING JOB SECURITY!!!

      There is nothing easier than writing perl code that only YOU can understand. Even if it is perfectly documented.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
  12. Re:Perl standards by Sun+Tzu · · Score: 2

    Perhaps it is the ultimate fate of perl to encompass all standards, making it the single most standard development language! ;)

  13. The push from Microsoft by yzorderex · · Score: 4

    is the best thing that could happen to Microsoft. With Win32-API and Win32-GUI both working nicely the OS is much more accessible and programmable. When Microsoft starts shipping Perl as a part of their standard distribution Perl will hit desktops worldwide and its usage will probably increase by an order of magnitude, Win-Win. (Dave Grove may have a heart attack though, Hi Dave! :-))

    --

    Just another perl hacker in Bangkok
  14. Perl Standards by RTMFD · · Score: 4

    An excellent article by a man who obviously calls 'em as he sees 'em. The OO paradigm promised to save the world of software engineering from bugs, complexity, and maintenance difficulties, but if the last 5 or 6 years are to be considered as indicators for future performance, it's not worth the hype. Although Perl is often accused of having a "bolted-on" OO interface, the base language is stable, supported, and widely used. Standards will only help to push its acceptance with the suits.

    Personally, I'd prefer to rely upon a language that delivers on the promise of "write once, run anywhere" :) In my experience, Perl does just that.

    Flames to /dev/null and let the language holy wars begin!

    1. Re:Perl Standards by Imperator · · Score: 2

      Actually, I've seen large OO projects that worked very well. I've also seen large non-OO projects that worked very well. But over the last 5 or 6 years overall software quality has decreased, with the exception perhaps of free software (the majority of which is C or its generate cousin _GNU_C). It's hard to tell whether OO projects have been doing better or worse, because there's been so much more buggy code across the spectrum.

      --

      Gates' Law: Every 18 months, the speed of software halves.
    2. Re:Perl Standards by jilles · · Score: 4

      "Maybe I still am missing the boat on OO, but at least I'm in good company. =)"

      Exactly, you just found another guy who missed the boat. This guy is smart enough to not completely dismiss python and java as useless but from the interview it is quite clear that you won't find him programming in either language (to put it mildly).

      For me OO is also something of the past. But at least I'm not stuck in the procedural/machine oriented paradigm of thirty years ago (when OO was the hot new thing). Personally, I find modern ideas such as aspect oriented programming, subject oriented programming or even intentional programming much more interesting.

      Perl is interesting in that sense because it is probably flexible enough to extend it to support either of those. On the other hand its syntax will probably always be a major obstacle for any serious adoption. Also performance is an issue (more than in Java) if you start doing serious development.

      Java at the moment is a much more mature language, perhaps due to the rigorous control of SUN over it. However, I think institutions like ISO mover too slow to keep up with the rapid developments. A standardized version of Java of three years ago would be close to useless to me. I suspect the same goes for perl. Like it or not, SUNs control of the Java language has prevented fragmentation and effectively caused it to be an industry standard with support for a large number of platforms.

      Finally a wise quote:
      "When you have a hammer, every problem seems a nail"

      I think this applies equally to either perl, vb, c(++), java, fill in you're favorite language. When developing device drivers stay away from visual basic. When developing e-commerce websites: don't bother using c. Also beware that languages and their accompanying libraries are under development. Two years ago Java was not good to do anything, now it is rapidly becoming the language of choice for number of domains (most notably web development).

      Don't use one hammer but educate yourself to be able to use the appropriate tools for the job at hand.

      --

      Jilles
  15. There is a perl standard by howard_wwtg · · Score: 4
    There is a Perl standard out there. Has been from the beginning.

    It is called Larry Wall.

  16. Sun and Java standardization by The_Messenger · · Score: 2
    I was one of many who were miffed when Sun decided to withdraw Java from the standards process. An international Java standard would not only make it easier to create Java development software, but would make it even easier to call Microsoft on their nonstandard "features" in J++. But Sun, being the Microsoft wannabes they are, probably that by making Java a standard, they would lose some of their now almost complete control over the language. Sun's published Java specs should easily provide the beginnings for a Java standard; why else would they have changed their mind?

    Getting offtopic, I would like to congratulate BSDi on their plans to bring Java 2 to FreeBSD. After a year of pestering Sun about this, and a few months of bothering IBM, FreeBSD will finally get the Java support it deserves. After the BSDi purchase of Walnut Creek, I often said that perhaps BSDi would put more "corporate" pressure on Sun to release JDK1.2 for FreeBSD, but this is a most unlooked-for and welcome development.

    (Now if only they would lower the BSDCon prices... )

    And re: "Perl Language Subcommittee" -- I thought that Larry, Randall, and Tom were the committee. ;-)

    ---------///----------

    --

    --
    I like to watch.

  17. evaporating standards by Jafa · · Score: 5
    I thought his comment on evaporating standards was hilarious and sadly right on the mark! To quote:

    1980's paradigm: If it's worth implementing once, it's worth implementing twice.
    1990's paradigm: Ship the prototype!
    2000's paradigm: Ship the idea!

    Jason
  18. The inevitable result of perl standardization... by Shoeboy · · Score: 4

    The ANSI Perl standard recognizes that "there's more than 1 way to do it." Specifically, the standard outlines 123 ways to do it -- see appendix c. Additional methods are "implementation defined."
    --Shoeboy
    (former microserf)

  19. micro~1 is paying for it by yzorderex · · Score: 2

    Good move too, IMO. Anything proprietory will be in the plug-in, ActiveState will own it and why bother to open source the code? They might open the API so people can add cool stuff but plug-ins to Visual Studio are so abundant (30 or so things in there I have no idea what they do) its evident that rocket science it ain't and I'm not sure why you'd bother.
    Documentation will be better and newless cluebies won't be posting I clicked on my program but the box closed so fast I donno what happen please help me type questions. Perl doesn't have a GUI, this will do it.
    I want a menu item to search for modules and there could be an Active Update, heheheehe check ActiveState for new versions of any modules every time I boot up. :-))
    Biggest impact may be a large upsurge in background programs on Win32 doing housekeeping, updating personal news pages, instant flame response forms if someone happens to mention Python on slashdot :-)). Stuff like that.

    --

    Just another perl hacker in Bangkok
  20. When I was a youngun... by pornking · · Score: 4


    Things were were always better in the old days, weren't they?

    • Remember how horribly everything broke when dos 4.0 came out?
    • Was Windows 95 really worse than windows3.1?
    • I think the Denver airport has been 5-6 years by now.
    • Every version of Netscape has been riddled with bugs.
    • Is Motif better than GTK?
    • X Windows is the defacto standard for unix displays. Is this really a good thing?
    • Do you actually like the design of NFS?
    • What about MacOS 6?

    What you have is a gut feeling that things used to be better because you only remember the good stuff. You remember how great Wing Commander was while forgetting that it took you 3 hours to figure out the config.sys and autoexec.bat for the boot disk.


    Now, the specific time frame being discussed is 5-6 years. Would you rather use Windows 95? As for unix, would you rather use SunOS? I remember some epic battles with xf86config under Linux. Was Netscape 1.1 really less buggy than Netscape 4.7?

    --
    pornking
  21. Re:Op Codes! Hell Yeah! by ph43drus · · Score: 2
    Assembly is totally worth learning. Eventually you'll do such things as start to shudder everytime you right `for' or `while' as you realize that everytime you loop, your superscalar processor is going to clear its pipe and drop in performance...

    The point is, you realize how bad your code really is ;) Hopefully, it will make you a better programmer, even if you very rarely use assembly.

    Oh yeah, and the line noise code, well let's just say it can win you prizes (see: Obfuscated Perl Contest, and the IOCCC). Not that I'm encouraging this or anything.

    Jeff

  22. Sadly Ilya has retired by tilly · · Score: 2

    His parting message.

    Sad. But he and Tom C had one too many flamewars and he has left.

    Incidentally Perl has a standard. It is the documentation. The cause of said flamewars is that Tom considers the documentation a standard and Ilya constantly wanted to play around with new features, add new constructs, etc.

    Cheers,
    Ben

    PS Trivia. If $a is an anonymous subroutine then $a->(@args) calls the subroutine with those arguments. This is very useful because $handler{$foo}->($bar) is far cleaner and more understandable than &{$handler{$foo}}($bar). OTOH I am amused that such a nice feature got included in Perl on a bar bet...

    --
    My usual seat in the cluetrain is at A HREF="http://pub4.ezboard.com/biwethey.ht