I know I'm off the original topic, but the original topic wasn't "Let's rip on PERL" either.
And if I can add to my argument, I challenge anyone to write a faster web transaction system than mod_perl would provide or better yet, Catalyst. You could argue ASP.NET on IIS6 given its deep integration in to the OS and native threading model, but I'm only considering web code that works in all web browsers. (Ruby on Rails...maybe). ________________________________ From: Brandon Mitchell [mailto:[EMAIL PROTECTED] Sent: Thursday, April 20, 2006 11:27 AM To: Garrett P. Taylor Cc: [email protected] Subject: Re: [RLUG] Re: can lisp do what perl does easily? I completely agree with everything you have said, here - apart from the total lack of "reading for comprehension" skill. The discussion (indeed the original text) was referencing perl's inappropriateness and complete lack of coherency as it applies to *major work*. Not one-off jobs. If you are not subscribed to the list, perhaps you missed the previous commentary between Brian and myself, but feel free to catch up with the archive <http://lists.rlug.org/pipermail/rlug/> . Or perhaps you missed the original article. Here's the key point: put simply: you can commit any dirty hack in a few minutes in perl, but you can't write an elegant, maintainabale program that becomes an asset to both you and your employer; you can make something work, but you can't really figure out its complete set of failure modes and conditions of failure. Note that Naggum recognizes (and I agree - apparently, so do you) the hackishness of perl and the appropriateness of the language for quick and dirty garbage code. The fundamental principle is not whether you or I *could* hack together a quick script to parse an ancient flat-text file and generate a nifty graph of the data for the PHB, but whether you or I *should* attempt to use the language for something less trivial. On 4/20/06, Garrett P. Taylor <[EMAIL PROTECTED]> wrote: > I'm stepping in to defend PERL. > > PERL is the official language of "gettin' 'er done". You've got 10 > minutes to accomplish a one-time task and you don't have time to sit and > plan out sophisticated classes with polymorphism in Java. You have to > connect to several different completely unique data sources so you can > hit up CPAN for modules that facilitate it. Write some sophisticated > data structures leveraging PERL's references. Pipe the output to a big > number-crunching program that someone hand coded in x86 assembly and > you're finished. > > No other langauge begins to approach that kind of versatility or if it > does it runs like a mule or takes forever to create code. PERL doesn't > promote the cleanest source code and basically throws everything you > learned in college out the window with its loose data types and hacked > attempts at objects. But decently written PERL code is only about 10% > slower than C and it gets things done quickly, efficiently, and without > a lot of pain. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Wayne Root > Sent: Wednesday, April 19, 2006 8:04 PM > To: [email protected] > Subject: Re: [RLUG] Re: can lisp do what perl does easily? > > Brandon Mitchell wrote: > > Fellow RLUG'ers, > > > > This flash from the recent past showed up on reddit today. Even if > > you're interested in niether Lisp nor goat vomit, it always provides a > > > good read. Take heart all you silly *cough*C++*cough* programmers out > > there! ;-) > > > > > Actually, I probably don't know EVERYTHING there is to know about goat > vomit, so I just might be interested.......... > > http://www.underlevel.net/jordan/erik-perl.txt > > > > -- > > If UNIX doesn't have the solution you have the wrong problem. > > UNIX is simple, but it takes a genius to understand it's simplicity. > > > > _______________________________________________ > > RLUG mailing list > > [email protected] > > http://lists.rlug.org/mailman/listinfo/rlug > > > > > > > > > > > > > > > > > _______________________________________________ > RLUG mailing list > [email protected] > http://lists.rlug.org/mailman/listinfo/rlug > > > > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient (s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender via reply email and destroy all copies of the original message. > > > _______________________________________________ > RLUG mailing list > [email protected] > http://lists.rlug.org/mailman/listinfo/rlug <http://lists.rlug.org/mailman/listinfo/rlug> > -- If UNIX doesn't have the solution you have the wrong problem. UNIX is simple, but it takes a genius to understand it's simplicity. _______________________________________________ RLUG mailing list [email protected] http://lists.rlug.org/mailman/listinfo/rlug
