Slashdot Mirror


Perl 5.16.0 Released

An anonymous reader writes "Perl 5.16.0 is now available with plenty of improvements all around. You can view a summary and all the change details here. With Perl on an annual release schedule, and projects like Mojolicious, Dancer, perlbrew, Plack, and Moose continuing to gain in popularity, are we in the middle of a Perl renaissance?"

192 comments

  1. Whatever happened to Perl 6? by BitterOak · · Score: 5, Interesting

    I love Perl, but I'm curious. Whatever happened to Perl 6? I remember hearing about it way back when I was in grad school, which was a long time ago.

    --
    If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    1. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 1

      That is a very good question!

      https://en.wikipedia.org/wiki/Perl_6

    2. Re:Whatever happened to Perl 6? by Chemisor · · Score: 0

      The same thing that will happen to Windows 8.

    3. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 2, Informative

      Perl 6 is quite a departure, with many breaking changes from 5. People had code written in 5, and 6 became moored in WIP status for the last 6-x years.

    4. Re:Whatever happened to Perl 6? by vlm · · Score: 5, Funny

      The problem with trying to do absolutely everything is it takes awhile to implement.

      http://perl6.org/compilers/features

      Its kind of like that Arthur Clarke story "The Nine Billion Names of God". If, one night, you glance at the sky and see the stars start going out, you'll know that someone has finally implemented all the Perl6 features. Either that, or its cloudy and going to rain.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    5. Re:Whatever happened to Perl 6? by Surazal · · Score: 4, Informative

      I love Perl, but I'm curious. Whatever happened to Perl 6? I remember hearing about it way back when I was in grad school, which was a long time ago.

      Perl 6 isn't dead, per se. A quick google search shows that there are a few implementations running around, although none are even close to production-ready yet. Here's the Perl 6 portal, in case you were wondering.

      I did run and download one of the more complete implementations, and part of the problem I think is that perl 6 is not ANYTHING like perl 5. The reason I use perl at all, and the only reason I still use perl 5 TO THIS DAY is the regex capabilities. They completely ripped that out of perl 6 and re-implemented it to make it more user-friendly, and they did so poorly, IMHO. Instead of calling htis perl 6, they should have named it something completely different. Call it "perl" does a disservice to what made perl so powerful in the first place.

      --
      --- Journals are boring; Go to my web page instead
    6. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      It will eventually be released on time? Seems like the opposite of what is happening with Perl 6.

    7. Re:Whatever happened to Perl 6? by vlm · · Score: 5, Interesting

      became moored in WIP status for the last 6-x years.

      12 years, not 6.

      The killer is no one in the perl dev community wants it. This says it all "Backward compatibility with earlier versions of Perl is not a goal". The problem is I don't love perl because of its syntax, although some of it is pretty cool, I love it because of the CPAN which does all my work for me. All my problems seem to be solved by combining at most ten or so CPAN modules. Its kind of like how the whole world is built out of only a hundred or so elements... if I wrote a perl program that used 100 CPAN modules, the result would be a new universe would spring into being, like the big bang. Or something like that.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    8. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      Perl 6 is still being worked on, but it's more of a proving ground for new features and new ideas. It'll be ready when it's ready. Meanwhile, many of the good ideas from Perl 6 have made their way into Perl 5 releases. Useful things such as Moose, smart matching, and other things. Hopefully others will reply with more details.

    9. Re:Whatever happened to Perl 6? by Jeremiah+Cornelius · · Score: 1, Troll

      Make no mistake, despite those who'd predict an "Epoch fail", Perl 6 is the future - and it always will be.
      The fate of Perl 6 is tied to that of IPv6. Widespread adoption of each is expected at the same rough timeframe.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    10. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      I am convinced that if they called it "Butterfly, from the minds which brought you Perl", it would be out the door already

    11. Re:Whatever happened to Perl 6? by cant_get_a_good_nick · · Score: 2

      This scares me. The fact that there are two compilers (which sows confusion) and none is feature complete... and it looks like Parrot was dropped.

      This is beginning to look like the HURD. A lot of thrashing around for cool features, nothing ever released.

    12. Re:Whatever happened to Perl 6? by chromatic · · Score: 5, Interesting

      ... part of the problem I think is that perl 6 is not ANYTHING like perl 5.

      The parts of Perl 6 I like are a lot like Perl 5, and the parts I really like are much better than Perl 5.

      ... the only reason I still use perl 5 TO THIS DAY is the regex capabilities. They completely ripped that out of perl 6 and re-implemented it to make it more user-friendly, and they did so poorly, IMHO.

      I like Perl 6 grammars far, far more than I like Perl 5 regex. That's one of the best parts of Perl 6. Regex as borrowed from Unix and enhanced over the years have accumulated a lot of mutually incomprehensible cruft. Perl 6 cleans that up.

      The problem with Perl 6, of course, is that no implementation is anywhere close to practically useful. Almost twelve years after the Perl 6 announcement, there's still no reason to hold your breath.

    13. Re:Whatever happened to Perl 6? by chromatic · · Score: 4, Informative

      If that scares you, cover your eyes: there are more than two compilers.

      ... it looks like Parrot was dropped.

      Not exactly. The Rakudo (Perl 6 on Parrot) people want to write a VM independence layer and port that to multiple VM backends.

      Don't ask me to explain that.

    14. Re:Whatever happened to Perl 6? by zmughal · · Score: 5, Interesting

      As far as the matching capabilities of Perl 6, I think they're trying to do something that will advance the state-of-the-art in terms of programming langauge integration in the same way that Perl 5's regex did. The Perl 6 rules are similar to the tricks and hacks that people do with regular expressions to build up full grammars. By separating out the parts into logical components, you will get better readability and reusability. Not only will we get cleaner text processing, but this (along with the VM architecture) will aid the development of DSLs that will extend the language into an exciting future.

      Yeah, it's some good Kool-Aid and the Perl community been waiting for a while, but bringing these ideas into a production-ready language isn't trivial. I'm still using Perl 5 because of CPAN, but I feel that Perl 6 will eventually get to the same level especially with a source-to-source compiler. The hardest part would be dealing with native-code bindings.

    15. Re:Whatever happened to Perl 6? by Jeremiah+Cornelius · · Score: 1

      Oh, BTW: Hey, Perloids! Thanks for the unecessary version precision! I had a whole surplus of ".0"'s hanging around, clogging the undersides of my keyboard. Now I can disperse them, almost at will in referencing this release. :-)

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    16. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      You mean "epic", not "epoch". Fail!

    17. Re:Whatever happened to Perl 6? by Jeremiah+Cornelius · · Score: 1
      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    18. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      woosh

    19. Re:Whatever happened to Perl 6? by skids · · Score: 1

      As far as the matching capabilities of Perl 6, I think they're trying to do something that will advance the state-of-the-art in terms of programming langauge integration in the same way that Perl 5's regex did.

      It's also one of the more functional feature sets already. Very useful if speed is not your priority.

      For people that actually enjoy learning new things rather than endlessly traversing the March of Progress, following Perl6 development is very refreshing.

    20. Re:Whatever happened to Perl 6? by JonySuede · · Score: 1

      have a look at Apache camel : http://camel.apache.org/enterprise-integration-patterns.html
      I have the feeling that it is the kind of problems you have to solve...

      --
      Jehovah be praised, Oracle was not selected
    21. Re:Whatever happened to Perl 6? by Crypto+Gnome · · Score: 1

      Sorry folks, this version "number" as described in the above article is actually an artefact of Zero Terminated String (mis)representation.

      The ACTUAL version is correctly displayed 5.16.

      --
      Visit CryptoGnome in his home.
    22. Re:Whatever happened to Perl 6? by Crypto+Gnome · · Score: 1

      Almost twelve years after the Perl 6 announcement, there's still no reason to hold your breath.

      The real reason why Perl6 hasn't been completed ready for production is that some aspects are dependent on (some of) those same people who are holding their breath.

      --
      Visit CryptoGnome in his home.
    23. Re:Whatever happened to Perl 6? by bill_mcgonigle · · Score: 1

      "Backward compatibility with earlier versions of Perl is not a goal".

      Have listen to the FLOSS Weekly interview with the fellow working on Rakudo. They do intend to get perl5 modules running.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    24. Re:Whatever happened to Perl 6? by zedeler · · Score: 1

      I am afraid that Perl 6 is becoming more of a social experiment in stead of a useful programming language. Unfortunately, because some of the fundamental ideas are really novel.

    25. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      You're right. It's purely a marketing problem. Perl needs an image makeover, as I posted somewhere else here, so it becomes the latest fad flavor. Build it and they will come.

    26. Re:Whatever happened to Perl 6? by jones_supa · · Score: 1

      The problem with trying to do absolutely everything is it takes awhile to implement.

      http://perl6.org/compilers/features

      That list shows "Rakudo" having most of the features in place already...

    27. Re:Whatever happened to Perl 6? by TheLink · · Score: 1

      Yeah what I'd actually want is for someone to do to Perl 5 what Google did with Javascript: make it run much faster.

      --
    28. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      became moored in WIP status for the last 6-x years.

      12 years, not 6.

      Maybe x=-6.

      Didn't think about that, did ya'?

    29. Re:Whatever happened to Perl 6? by stderr_dk · · Score: 2

      and it looks like Parrot was dropped.

      Nah, he's only resting...

      --
      alias sudo="echo make it yourself #" ; # https://pipedot.org/~stderr & http://soylentnews.org/~stderr
    30. Re:Whatever happened to Perl 6? by vlm · · Score: 1

      And with only 12 years of development in, they've only got maybe another 10 to go. Excellent.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    31. Re:Whatever happened to Perl 6? by DuckDodgers · · Score: 1

      While I want to be able to use Perl6 today, writing software is not going to go away any time soon. If it takes another ten years for Perl6 implementations like Rakudo to be feature complete and another ten years for it to run as efficiently as Perl5, that's fine - developers twenty years out will have one hell of a fun and productive new tool at their disposal, and they can use it from then until the collapse of civilization.

    32. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      We won't see the kind of dramatic improvement that happened with Javascript because the existing implementation is already far better than early Javascript engines were. That said, there is still room for it to get better.

    33. Re:Whatever happened to Perl 6? by TheLink · · Score: 1

      Perl is slower than Javascript for many things- 30 to 100 times slower:
      http://shootout.alioth.debian.org/u32/benchmark.php?test=all&lang=v8&lang2=perl

      --
    34. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      Faster is always better but well written perl code is already generally as fast as its C counterpart + compilation time.

    35. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      Yes, and that's using v8, which isn't an "early Javascript engine".

    36. Re:Whatever happened to Perl 6? by bcrowell · · Score: 1

      The killer is no one in the perl dev community wants it. This says it all "Backward compatibility with earlier versions of Perl is not a goal".

      The first sentence would have more credibility if you had some evidence or if it wasn't stated so categorically as to be obviously false. I'm in the perl developer community, and I do want perl 6 -- I'm just not holding my breath for it to be usable very soon for real-world projects.

      The second sentence seems to be quoted from the WP article, but you made it misleading by chopping out the second half of the sentence:

      Backward compatibility with earlier versions of Perl is not a goal, though a compatibility mode is part of the specification.

      What this actually means, as I understand it, is that you won't be able to mix perl 5 and perl 6 code within the same module, but you will be able to mix perl 5 and perl 6 modules within the same project.

      I think what is really killing the momentum for perl 6 (or whatever weak momentum it ever had) is that a lot of people who want a better perl have hitched their wagons to ruby instead. If perl 6 had been just a little faster out of the gate (say reaching the point it's at 5 years ago), then a raw, buggy perl 6 might have interested a lot of people as an alternative to the relatively raw and buggy state of ruby 5 years ago. Ruby is competently built, but it's never reached a point where its implementation was of the same quality as perl 5. However, there's been a gradual process of steady improvement, and at this point it's getting more and more solid -- as opposed to perl 6, which has been almost-usable-for-real-work for 5 years.

    37. Re:Whatever happened to Perl 6? by WebCowboy · · Score: 1

      This scares me. The fact that there are two compilers (which sows confusion) and none is feature complete

      Why is that so scary or "confusing"? There are a lot of compilers for C and C++ out there, and they aren't all "Feature complete" (MSFT's C++ compiler for example is not fully C99 compliant and they don't seem in much of a hurry to make it so). Doesn't seem to me to indicate that a language or platform should be discounted.

      ... and it looks like Parrot was dropped.

      Can you give a citation showing this? A new release of Parrot came out just last week. It looks far from dropped--in fact it looks like a VERY actvie development community--they seel to put out a new release every month or so! Also, the latest Radoko compiler for Perl6 is only about a month old itself.

      I won't argue the point that the dev timeline is somewhere between "duke nukem forever" and "GNU HURD" in terms of release to market timelines. The devs do seem to be pursuing development of Parrot and Perl6 more in terms of an academic or research exercise than in putting out production code. However it is a complete misstatement to say Parrot has been dropped.

    38. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      It's not secret that a substantial amount of Rakudo development goes toward writing something intended to be a VM abstraction layer. The official party line is "To improve the potential of running on other VM backends".

    39. Re:Whatever happened to Perl 6? by youn · · Score: 1

      forget perl 6, what happened to perl 8, 9. 10... they should by at least at version 42 by now :)

      --
      Never antropomorphize computers, they do not like that :p
    40. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      > What this actually means, as I understand it, is that you won't be able to mix perl 5 and perl 6 code within the same module, but you will be able to mix perl 5 and perl 6 modules within the same project.

      Mixing modules within the same project has been working, on and off, fsdo "working", for a few years. Imo it's very likely the Rakudo team will make this level of integration work reasonably well this year. (If you're interested in the details, visit #perl6 and ask about Rakudo, 6model, Zavolaj, and Blizkost.)

      Mixing Perl 6 and Perl 5 (mimics perl5) in the same module will come later.

    41. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      > It's not secret that a substantial amount of Rakudo development goes toward writing something intended to be a VM abstraction layer.

      NQP can be described as a VM abstraction layer, but it's important to note that the reason it was introduced, and is being developed, has little to do with a desire to have a VM abstraction layer.

      In fact, the Parrot (VM) team plans to backport NQP to Parrot. If/when that does actually happen, Rakudo and Parrot will both be able to have their cakes and eat them -- Rakudo will have a nice architecture for running on both Parrot and other VMs, with Parrot's relative performance enhanced by its native adoption of NQP, and Parrot will have a nice architecture for mixing the diverse object models of the likes of Python, Ruby et al, due to the strengths of the 6model built in to NQP. (And if the Parrot team does not have sufficient tuits this year, Rakudo will be fine anyway.)

      > The official party line is "To improve the potential of running on other VM backends".

      That's one of several justifications, and probably (hopefully, if the Parrot team can backport NQP this summer or fall) the least important.

    42. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      I trust Larry Wall's word on Perl 6 more than I do that of most other commentators.

      Searching the #perl6 logs, going back to 2005, Larry Wall has used the words "productize", "productizing", or "productization", four times:

      2007: "productizing the whole thing will take a goodly long time"

      2009: "productization doesn't happen magically, but is the result of a lot of hard work :)"

      2010: "I've specifically been shying away from anything resembling productizing"

      2012: "... the things we need to do to productize Perl 6 over the next year or two"

      If I were a betting man, I'd bet Perl 6 will be productized over the next year or two.

    43. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      Imo it's very likely the Rakudo team will make this level of integration work reasonably well this year.

      On what do you base this opinion? Rakudo's had more than one proof of concept that never made it much past the proof of concept stage before bitrotting before.

    44. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      ... it's important to note that the reason it was introduced, and is being developed, has little to do with a desire to have a VM abstraction layer.

      ... except for the fact that almost every time its lead developer talks about it, he talks about how it'll help porting to other VM backends (and that it explicitly exists to minimize the amount of Parrot surface area exposed to Rakudo).

      In fact, the Parrot (VM) team plans to backport NQP to Parrot.

      I think you're confused. The Rakudo team has written at least three things called NQP and all of them run on Parrot. In fact, that's one of the biggest problems of Rakudo: writing code that Parrot has to support and then abandoning it and complaining that Parrot can't move fast enough for Rakudo because Parrot has to support Rakudo's abandoned tools.

    45. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      If I were a betting man, I'd bet Perl 6 will be productized over the next year or two.

      Rakudo Star was supposed to be a product two years ago. That was the point of Rakudo Star. It's still not a product now.

    46. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      The first Rakudo Star shipped nearly two years ago and has been updated many times since. The latest version, which once again demonstrates a lot of progress in just 4 weeks, is due out in a day or two.

      These versions of Rakudo Star were and are not the "productized" Perl 6 of which Larry spoke. They were never supposed to be. The point of Rakudo Star was and is to be a bundle of bits -- latest compiler, modules, etc. -- that were/are sufficiently "usable and useful for early adopters" that the Rakudo team would get feedback that helped drive development.

    47. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      > ... except for the fact that almost every time its lead developer talks about it, he talks about how it'll help porting to other VM backends (and that it explicitly exists to minimize the amount of Parrot surface area exposed to Rakudo).

      I follow #perl6, and jnthn frequently mentions NQP and almost never mentions how it'll help in porting to other VM backends or that it minimizes Parrot exposure.

      Perhaps you mean presentations? I think it would be dumb of jnthn to do a presentation of NQP and not talk about how it'll help in porting to other VM backends. The fact remains that these aspects were not the driving reason for doing NQP.

      > I think you're confused. The Rakudo team has written at least three things called NQP and all of them run on Parrot.

      No, I'm not confused. More...

      > In fact, that's one of the biggest problems of Rakudo: writing code that Parrot has to support and then abandoning it and complaining that Parrot can't move fast enough for Rakudo because Parrot has to support Rakudo's abandoned tools.

      I hear that's your perspective. But to quote the current Parrot lead dev:

      "Rakudo isn’t the problem and never has been. ... Some people have said that Rakudo has been an impediment to Parrot development, or that they are a reason why Parrot has problems and why the pace of development has been so slow. I think that’s a short-sighted sentiment. ... In short, whatever negative feelings some parrot devs think they have about Rakudo is just a smoke screen. ... We need to focus as much effort as we can to be a better VM for Rakudo Perl6, including moving as much custom code from the NQP and Rakudo repos as possible into Parrot core to lower barriers and increase integration."

    48. Re:Whatever happened to Perl 6? by TheLink · · Score: 1

      Yes and what I said was:

      Yeah what I'd actually want is for someone to do to Perl 5 what Google did with Javascript: make it run much faster.

      Not run faster than early javascript engines. Try to keep up please.

      --
    49. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      Faster is always better

      Not what she said.

    50. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      it looks like Parrot was dropped.

      My God, does Stallman know?

    51. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      The point of Rakudo Star was and is to be a bundle of bits -- latest compiler, modules, etc. -- that were/are sufficiently "usable and useful for early adopters"...

      My business had a product to release based on Rakudo Star two years ago. (We were preparing to ship it in April 2010.) We had customers ready to pay for that project.

      We never shipped that product because Rakudo Star was neither usable nor useful for our purposes. It still isn't.

    52. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      jnthn frequently mentions NQP and almost never mentions how it'll help in porting to other VM backends or that it minimizes Parrot exposure.

      Read 6guts.

      We need to focus as much effort as we can to be a better VM for Rakudo Perl6, including moving as much custom code from the NQP and Rakudo repos as possible into Parrot core to lower barriers and increase integration.

      I've fixed enough of the custom code in Rakudo that I feel confident in saying that big wad of code was a big part of the problem.

    53. Re:Whatever happened to Perl 6? by robsku · · Score: 1

      "Backward compatibility with earlier versions of Perl is not a goal".

      Have listen to the FLOSS Weekly interview with the fellow working on Rakudo. They do intend to get perl5 modules running.

      Yeah, that quote, taken out of contest and without even mentioning the planned compatibility mode (mentioned in same paragraph) is misleading and I can only assume that the poster is either really bad reader or just trolling.

      --
      In capitalist USA corporations control the government.
    54. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      > Read 6guts [wordpress.com].

      I do, and just did again. Consider what is currently the first match of "NQP":

      "QAST really is a simultaneous port to NQP, leaving out things we came to realize were bad or unrequired, adding much better 6model integration, unifying the notion of “ops” somewhat, improving native type support and taking advantage of native types during its implementation to get the AST nodes more compact, so we can save on memory during the compilation. Additionally, it will unblock masak++’s work on quasi splicing in macros, and is a step towards Rakudo targeting other backends being a reality rather than a nice idea."

      Note that he mentions "targetting backends" *last*.

      > I've fixed enough of the custom code in Rakudo that I feel confident in saying that big wad of code was a big part of the problem.

      Parrot's current lead dev has a starkly different opinion:

      "6model is far superior to what Parrot provides now, and is superior for all the languages that we’ve seriously considered in recent months: Cardinal (the Ruby port) was stalled because it needed features only 6model provided. Puffin (the Python port) needed 6model. Jaesop, my new JavaScript port, is going to require 6model because the current object model doesn’t work for it. These represent some of the most important and popular dynamic languages of the moment, and all of these would prefer 6model over the current Parrot object model by a wide margin. So ask yourself why the Rakudo folks were forced to develop 6model elsewhere, and why Parrot hasn’t been able to port it into its core yet. Ask yourself that, and see if you can come up with any reasonable answer. I can’t find one, other than “oops, we screwed up BIG”."

    55. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      Parrot's current lead dev has a starkly different opinion

      Christoph is Parrot's current leader, not Andrew. While I agree that Parrot needs 6model (and 6model is an improvement over the previous object system), the reality is far, far more complicated than Andrew makes it sound.

      In particular, Parrot adopting 6model wholesale even last year (as most of us wanted) would have been highly difficult because 6model was still in flux, because Parrot still had to support a lot of abandoned Rakudo tools which relied on the old semantics, and because Jonathan was dragging his feet on helping Parrot adopt 6model.

      Note that he mentions "targetting backends" *last*.

      You've changed your argument from "He rarely or never mentions it" to "He mentions it last in a list which isn't obviously ordered in terms of descending priority."

    56. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      To date, Rakudo Star has been useful and usable only for some purposes in some situations. Think in terms of something like a Perl 6 script for processing ABC music notation (http://justrakudoit.wordpress.com/2012/05/21/optimizing-abc2ly-pl/), not business ventures.

    57. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      > Christoph is Parrot's current leader, not Andrew.

      Thanks for that correction. And wow. (Andrew must have written more than 95% of http://planet.parrotcode.org/!)

      > Parrot still had to support a lot of abandoned Rakudo tools which relied on the old semantics

      Why? And how is that Rakudo's fault?

      > Jonathan was dragging his feet on helping Parrot adopt 6model.

      Oh. Wow. I'll report back here on what he says about this to me.

      > You've changed your argument from "He rarely or never mentions it" to "He mentions it last in a list which isn't obviously ordered in terms of descending priority."

      Er, no.

      Heh. I think there's at least a little humor in the parallel with the thread containing http://perlmonks.org/?node_id=950411 in which you wrote "You're of course welcome to summarize (in this case, very wrongly) what you think I said provided you disclaim it as your (wrong) opinion, but putting it in quotes? As if I'd ever thought that, let alone said or written it? That's malicious and libelous.".

    58. Re:Whatever happened to Perl 6? by Anonymous Coward · · Score: 0

      I said I'd report back with jnthn's response to chromatic's suggestion he dragged his feet on helping Parrot adopt 6model. In the interests of decorum, I've changed my mind about that.

    59. Re:Whatever happened to Perl 6? by chromatic · · Score: 1

      In the interests of decorum, I've changed my mind about that.

      How tacky.

  2. Ahhh by future+assassin · · Score: 0

    PERL spend many a night modifying my Everyauction script/site.

    --
    by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
  3. No by Anonymous Coward · · Score: 0

    The Renaissance was characterized by lots of people learning and contributing to a wide variety of ideas, skills, sciences, and arts.

    Perl is one language that does things on one kind of device.

    1. Re:No by vlm · · Score: 2

      LOL apparently you've never seen the Perl6 feature list, which can be summarized to "implement every programming concept known to mankind", or the CPAN which is "everything that can be turned into (what amounts to) a library, turned into a library and ready to freely download".

      Its the ultimate glue language.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    2. Re:No by Anonymous Coward · · Score: 1

      Is Perl the "Ron Paul" of general purpose scripting languages?

      *ducks*

    3. Re:No by X.25 · · Score: 5, Insightful

      Perl is not coming back. Get over it and learn something else.

      It never went anywhere, so why would it need to come back?

    4. Re:No by Anonymous Coward · · Score: 0

      Hmm. I use perl at least weekly. I might not write many important programs with it, but for the quick and dirty script or one-liner, it is still a useful thing to know. But, yeah ultimately it would be a good idea to broaden ones horizons a bit and pick up another scripting language.

    5. Re:No by Anonymous Coward · · Score: 0

      Don't know where you have been, but Perl is the only worthy language for a server.

      Anything else is wasted cycles.

    6. I"m not sure what "not coming back" signifies. We run a decently large Perl codebase. We add some new features (nothing big) new code tends to go to python (though some new perl stuff). But changes in the tools as we maintain the codebase is important to us.

    7. Re:No by h4rr4r · · Score: 5, Informative

      Coming back?

      It never left, I used it everyday.

    8. Re:No by gatesstillborg · · Score: 1

      Perl is built up with a fair amount of exotic, idiosyncratic constructs, but its core features (datastructures and syntax), do it better than any of them. If you just resist getting sucked into all its esoteric aspects, which some quirky elements (with some questionable motives) seem to push so hard, then you'll do just fine.

      "You take what you need and you leave the rest." Robertson (Helm)

    9. Re:No by doti · · Score: 2

      Right now I am (should be :) writing Perl code, and being paid for it.
      And it's a big and important project, not just some utility scripts.

      I also write one of my main pet projects in Perl.

      --
      factor 966971: 966971
    10. Re:No by Reality+Master+101 · · Score: 1

      I use Perl nearly every (damn) day, on a very old codebase project. There are things about Perl I like, but there are also things that I really despise. Not through fault of Perl, really -- it's simply old, slow (yes, slow) and outdated compared to other modern languages.

      There is no way I would start a new project in Perl, and the only people who would are people who are willfully ignorant of the rest of the industry. Perl is beyond its life. There is nothing it does better than other languages, and there are a whole hell of a lot of things it does much, much worse.

      --
      Sometimes it's best to just let stupid people be stupid.
    11. Re:No by FrootLoops · · Score: 2

      Coming back?

      It never left, I used it everyday.

      Hah, you got modded informative instead of funny.

    12. Re:No by Junta · · Score: 2

      The reason I like perl is that it is 'good enough' and the people that would screw with it to make it inconsistent are all off on either perl6 windmill chasing or other languages. I will admit to some unfortunate ignorance of ruby, but at least with python, while I find it a commendable language, they have been much more aggressive about incompatible changes than perl5. A program written against perl 5.4 runs fine with perl 5.16. However, in my experience code written against python 3.0 might not work quite right with 3.2 without some tweaks.

      In terms of *nix friendly scripting languages, ruby, perl, and python are the only choices with a sufficiently rich set of libraries available to do things.

      Besides that, perl is serviceable. It allows programmers to employ unreadable syntax, but coding discipline can mitigate that. Generally poorly readable perl code can be written readably. Part of this is terse syntax to enable simple one-liners in a *nix pipe chain. Python isn't exactly a language amenable to that. However, perl syntax accomodates more verbose, readable style to be comparable to python in more sophisticated scripts. Compare this with awk, which also has excellent properties on CLI, but doesn't scale up to a 'real' program so well.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    13. Re:No by alantus · · Score: 1

      In my experience Perl is fast, less resource intensive than other interpreters such as Python, is really good for regular expressions and data structures, and it just gets the job done in a short development time.

    14. Re:No by DuckDodgers · · Score: 1

      I had forgotten that a lot of skilled Perl users use "perl -e (commands)" with piping to get things done. You're right, that's extremely handy and definitely not something you can do with Python.

      I think the perl6 windmill is worth tilting at - at worst it makes the people jousting more knowledgeable about writing interpreters and virtual machines, and gives ideas to the general community that improve other existing languages. That includes Perl 5, I understand some of the features in Perl 6 made it into Perl 5.14 and 5.16. If we have to wait another twenty years before Perl6 is rock solid, so what? Barring an unfortunate accident, I'll still be writing code then.

      As a linked topic, at my day job I work on Java. I don't have many opportunities to use Perl 5 for more than toy scripts to accomplish simple tasks. But I find the general mentality of the Perl 5 and Perl 6 community refreshing - a good mix of brilliance and practicality. My personal experience with the Java community is that there is intelligence and innovation around the edges but a lot of stale repetition and over-engineered solutions that choke on their own complexity in the mainstream. If I could figure out how to transition from Java development to Perl development without taking a 20% pay cut, it would be tempting.

    15. Re:No by happy_place · · Score: 1

      Perl is a beautiful language. I love the use of list operators and the concept of list context. Every symbol has meaning. No language does a better job of incorporating and taking full advantage of regular expressions. There are plenty of modules to assist in specific tasks, and because it doesn't enforce one programming paradigm, it allows those who use it the chance to be flexible and still maintain good structure if that's what's key. It takes some time to learn, but the benefits are rich and well worth the experience. The community is very mature, and there's a lot of free and minimally cost-based training available, without the fear of running to the edge of what's feasible or buggy. I highly suggest my favorite perl experts site: http://perlmonks.org/ if you want to learn the language. There are some amazing experts there, willing to share their knowledge and expertise, and thousands of tutorials and helpful comments.

      --
      http://www.beanleafpress.com
  4. Modern Perl book by Anonymous Coward · · Score: 4, Informative

    Chromatic's Modern Perl book is also available as a free download. It's useful for Perl programmers who want to know what's new in the Perl world in the last several years.

  5. Hard to get started by Anonymous Coward · · Score: 0

    Web development has changed so much that unfortunately you can't get started the way you could back in, say, 1999. I know because I tried it. Tried to go from PHP to Perl and kept running into 1) old Perl stuff with amazing documentation and tutorials and book and 2) new Perl stuff with a confusing mess of advice, opinions, and non-support from framework users. I was really looking forward to learning Perl, but for now I'm sort of stuck with PHP and CodeIgniter due to lots of current documentation and a very generous community.
     
    Can some /.er point me down the path toward modern Perl learning? Tried Mojolicious and Dancer and had to bow out; much too complex for me at this point. As I recall, the Dancer blog example was set up in such a way (using hashes, or something like that) that it was hard for a beginner to understand and extend.
     
    I'm also currently using a bit of Python and C, but deploying Python web apps is a gigantic pain in the mess.

    1. Re:Hard to get started by chromatic · · Score: 5, Informative

      Can some /.er point me down the path toward modern Perl learning?

      I have a bias, but I've had many positive responses to Modern Perl: The Book.

    2. Re:Hard to get started by vlm · · Score: 1

      Try some perl development the old fashioned way. Document a list of "PITA" about developing in perl. Simultaneously study at least one framework and slowly enumerate a list of "this is how framework X fixes the Y problem" ah "I know kung fu" or whatever. At some point those lists will converge. Then seamlessly start developing the new way using a framework.

      You can also have a lot of fun trying to implement your own homemade framework. Being a text processing language, making a MVC like system isn't too hard. Again, at some point your toy MVC will converge with some perl framework and away you go.

      I started doing RoR probably 5, maybe 6 years ago, and I agree, the learning curve for a framework is darn near vertical unless you're doing the overly simplistic demo apps... note demos are selected precisely because they make the framework look good, not because they're realistic. Eventually the insane vertical learning curve flattens out. Just like second semester calculus, sometimes you just gotta gut it out till you get it.

      You may be better off forgetting about "web development" which is a pretty huge and complicated solution space. Come back to it later. Go to projecteuler.com and solve a couple simple compsci algorithms in your new language. I am teaching myself Scala at this time, for the heck of it, by implementing the craziest solutions I can to some P.E. problems. I wish I had learned Ruby in full detail before I started to learn RoR, would have been a much smoother learning curve.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    3. Re:Hard to get started by drunkennewfiemidget · · Score: 1

      Slight bias indeed.

      The man page to Moose is a good one too.

      If you're in to web dev, the Definitive Guide to Catalyst is a good choice, too.

      Unfortunately, I have to write this with a caveat: getting Catalyst and Moose set up can take some time. If you apt-get install/emerge/yum/whatever it, you'll probably get an old version.

      If you install it from CPAN, it takes some time, since the two of them combine to require a craptonne of CPAN.

      That said, once they're installed, a working catalyst web app you can hack on is as simple as catalyst.pl AppName; cd AppName;scripts/appname_server.pl

    4. Re:Hard to get started by vlm · · Score: 3, Interesting

      Well that was embarassing. you don't want to see projecteuler.com. Try

      http://projecteuler.net/

      that works a heck of a lot better.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    5. Re:Hard to get started by Anonymous Coward · · Score: 0

      Can some /.er point me down the path toward modern Perl learning? Tried Mojolicious and Dancer and had to bow out; much too complex for me at this point. As I recall, the Dancer blog example was set up in such a way (using hashes, or something like that) that it was hard for a beginner to understand and extend.

      Stick with Mojolicious (or Dancer, but I like Mojolicious). There is a learning curve compared to "the old days" - but it's not because these frameworks are hard to use, it's because web development has moved on. Once you have some of the basic concepts down, you'll never look back.

    6. Re:Hard to get started by Anonymous Coward · · Score: 0

      I love perl and use it every day. I actually disagree with some comments about perl speed. In my experience people tend to slow their code by using a module every time one exists rather than looking for a module when they find themselves about to build a wheel.

      My only major complaint is multi-processing. Perl is very cumbersome in this regard. This is perl, there are a lot of language constructs that naturally lend themselves to multi-processing, the interpreter should multi-processing them out of the box.

    7. Re:Hard to get started by chromatic · · Score: 1

      Perl is very cumbersome in this regard.

      It can be, yes. The last two times I needed multiprocessing, I used Proc::Fork and WWW::Curl::Simple. These worked very well for me.

      A lot of people use AnyEvent quite effectively too.

    8. Re:Hard to get started by tangent · · Score: 1

      Take a look at Forks::Super. It's still a bit on the beta side, but useful enough for you to get real work done while you bang on the author to fix the remaining bugs. :)

  6. Short answer: No by Anonymous Coward · · Score: 0

    If my co-workers are anything to go by, absolutely anything starting with some equivalent of "#!/usr/bin/perl" or that contains the line "use strict;" is ultra-scary double-plus-ungood hate hate hate.

    Which is why I'll be employed here as long as I want, since I'm one of the few people who'll do dirty parsing work, and my weapon of choice is Perl. Heh.

    But, unfortunately, no, Perl won't pick back up soon. Shame. I sort of like the esoteric chaos of the language.

    1. Re:Short answer: No by Anonymous Coward · · Score: 0

      Shame. I sort of like the esoteric chaos of the language.

      Exactly. Perl has a real beauty to it. I really find it aesthetic, fast and stimulating to code with and there's virtually no capability that cannot be found pre-written as a module in CPAN. But oh no, now we all have to use fucking Python with its white space syntax.

    2. Re:Short answer: No by Junta · · Score: 2

      What's *really scary* is a perl script with '#use strict;'. Meaning they tried to use strict; but gave up on it.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:Short answer: No by stderr_dk · · Score: 1

      What's *really scary* is a perl script with '#use strict;'. Meaning they tried to use strict; but gave up on it.

      Did they use common::sense; instead?

      --
      alias sudo="echo make it yourself #" ; # https://pipedot.org/~stderr & http://soylentnews.org/~stderr
    4. Re:Short answer: No by Anonymous Coward · · Score: 0

      I've only ever seen a handful of perl code which I would consider to be anything close to, "a real beauty." Most perl code, by far, is tersely cryptic garbage which the author himself must use a decoder ring on six weeks later. THAT's perl's legacy; crytically terse garbage.

      Perl awesomely excels at quick one liners and one off filters, but it absolutely sucks for long term, highly maintainable code.

    5. Re:Short answer: No by Junta · · Score: 1

      No, they just can't figure out how to pass some of the checks and disable them. Generally upon investigation I find use strict complained for very good reason and I'm able to close out 'mysterious' bugs just by use strict.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    6. Re:Short answer: No by stderr_dk · · Score: 1

      The common::sense people claim it uses less memory than the combo, I'm currently using (mainly use strict; use warnings;), so I'm considering switching.

      If anyone has any input about use common::sense; vs. use strict; use warnings;, I would like to hear it.

      --
      alias sudo="echo make it yourself #" ; # https://pipedot.org/~stderr & http://soylentnews.org/~stderr
    7. Re:Short answer: No by Anonymous Coward · · Score: 0

      Exactly. I've generally found that even if use strict is complaining about something I'm doing intentionally I should probably be looking for an alternate implementation rather than working on how to dodge the use strict complaint.

  7. Coming back? by Anonymous Coward · · Score: 1

    Perl never went anywhere. Sure, it may not be today's new hip fad language, but it's widely used and supported.

    1. Re:Coming back? by rubycodez · · Score: 0

      it's just used for legacy things, it is not the choice of new projects, and a dozen years in and still Perl 6 not finished, it's clear Perl is just dying a slow death. It was great in the day, that day being late 1990s.

    2. Re:Coming back? by Junta · · Score: 1

      It is still used in new projects. IMO, Perl 6 being finished probably would kill the language. The reason perl5 is appealing is precisely because people are not screwing around with it in incompatble ways (they are inflicting that on perl6). The stabliity/compatibility, accumulated set of languages, and the fact the syntax is perfectly serviceable makes for a very solid scripting language choice, even for new projects.

      Just because some people do not view it as 'hip', doesn't mean it isn't a good, reasonable choice for new development.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    3. Re:Coming back? by dolmen.fr · · Score: 1

      IMO, Perl 6 being finished probably would kill the language.

      It won't. Perl 6 is a much more ambitious programming language, and as such will require more ressources (CPU, memory). Perl 6 is clearly directed to general programming while Perl 5 has always been useful as both a generic programming language and as a glueing tool for sysadmin tasks. The '-e' of Perl 6 will probably stay so slow that it will not be as useful as Perl 5 as a simple tool for small tasks.

    4. Re:Coming back? by Junta · · Score: 1

      I meant if Perl6 'succeeds' at making distros deprecate perl5, then perl is doomed as perl6 won't be interesting compared to other contemporary scripting languages without the stability of perl5.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  8. Like Perl, but Python dominates by Anonymous Coward · · Score: 2, Insightful

    .. for prototyping and scripting. I'm a non-coder working for a software house with highly experienced coders. I taught myself Perl and C. But none of these guys will use Perl. For anything. All they will use for scripting and prototyping is *Python*. They make the usual cliche jokes about Perl being unreadable etc. I'm really beginning to think that I wasted my time learning Perl.

    1. Re:Like Perl, but Python dominates by ThePhilips · · Score: 3, Insightful

      All they will use for scripting and prototyping is *Python*.

      NOT using Perl for prototyping IME is a good thing.

      Many of my program and libraries begin their life as proof-of-concept in Perl. And the problem is that from Perl implementation it is pretty much never possible to devise how much time it would take to implement C/C++/etc equivalent.

      I had totally bad cases like where I have spent 2 weeks writing a library in C++ for which Perl's equivalent took me only 30 minutes. As a proof-of-concept, Perl implementation could be a quick hack - but C++ has to be a production quality. With the vast utility of Perl many corner cases seem trivial and work easily without performance regressions - while in C/C++ one ends up feeling like reimplementing the wheel for every one of them.

      Perl is BAD for prototyping for C and C-like languages IMO. The difference between the languages and the libraries is way too great.

      P.S. I'm not sure how better it is in Python. It should be better: the utility of the Python is much more limited compared to the Perl.

      --
      All hope abandon ye who enter here.
    2. Re:Like Perl, but Python dominates by rduke15 · · Score: 1

      Whether you wasted your time depends on whether you can use what you learned occasionally, or whether you had fun learning it. But anyway, learning anything is seldom a waste of time.

      If your coders know several languages, and happen to not like Perl, that's OK. But if they know only a single language and really never use anything else, they are just not very competent and probably also quite boring.

    3. Re:Like Perl, but Python dominates by Junta · · Score: 1

      Basically, most of any scripting language pretty much makes you throw out the codebase when you go to C. Exploring a concept to assess feasibility can work, but don't expect to not have to nearly start over, just with the benefit of knowing which algorithms/development paths just won't pan out.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    4. Re:Like Perl, but Python dominates by flargleblarg · · Score: 0

      Perl is BAD for prototyping for C and C-like languages IMO. The difference between the languages and the libraries is way too great.

      That is a really really really really really lame reason not to use Perl, IMHO.

    5. Re:Like Perl, but Python dominates by serviscope_minor · · Score: 1

      If you're writing in "C/C++" then you're either writing C, or terrible C++, so no wonder it is taking you so long.

      Try using C++, or even C++11.

      --
      SJW n. One who posts facts.
    6. Re:Like Perl, but Python dominates by ThePhilips · · Score: 2

      Exploring a concept to assess feasibility can work, but don't expect to not have to nearly start over, just with the benefit of knowing which algorithms/development paths just won't pan out.

      My problem with Perl is precisely that: it is nearly impossible (or very time consuming) to implement conventional data structures like list or tree in Perl. One generally doesn't need them in Perl - but they pop up pretty often in C/C++/etc.

      Now, when prototype is implemented using the Perl's arrays and hashes, they are orthogonal to data structures C++ code it going to use. Assignment of arrays and hashes (even during their mutation in loop) is optimized well in Perl - but in C++, it would end up being a pretty dumb copy of large chunks of data. I see often the cases where prototype in Perl is managing task in fraction of second - while code dumbly 1:1 translated to C++ is taking seconds.

      Thus IME even for potential algorithm assessment Perl is not a good choice. Algorithms as they are implemented in Perl and in C/C++ end up being way too different. In Perl it is easy to base many things on hashes and they would perform great. OTOH, if prototype is followed closely, in C++ one would be simply overwhelmed by the resulting code complexity of managing so many (potentially different) associative containers. Turning problem up side down and trying to implement prototype in Perl without hashes (I did this several times too) is a real chore and by complexity pretty close to implementing the same prototype in C++.

      As it stands, I yet to find a language which is good for C/C++ prototyping. I have tried in past the Python, but was turned off by the lack of warnings and very poor performance. Lisp and some of its descendants theoretically are good candidates too, but I have none of them available in office.

      --
      All hope abandon ye who enter here.
    7. Re:Like Perl, but Python dominates by dolmen.fr · · Score: 1

      When I write quick scripts and prototypes I want things to work, and not discover at runtime that a typo in a variable name breaks.
      That's why I love "perl -c" combined with "use strict" and have abandonned Python a long time ago.

  9. Jumping the Ruby ship by Anonymous Coward · · Score: 0

    Everyone who switched from Perl to Ruby found out that Rubyist's (OK, Rails-ists really) are arseholes and are now returning to Perl.

    1. Re:Jumping the Ruby ship by Aighearach · · Score: 1

      Every single one, or just you?

  10. Re:Renaissance? by Jeremiah+Cornelius · · Score: 2, Funny

    Who said anything about dagos and cathedrals? That's a bazaar inference!

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  11. Parallax by hessian · · Score: 5, Insightful

    We're seeing Perl as having moved because we have moved. Perl has kept doing what it has always done at a high level of excellence.

    The market shifted. First, many Perl programmers shifted to PHP once the net decided security and economy of processing power were not goals on the table. Second, a lot of newer programmers are reliant on frameworks and other pre-built systems and learned the languages that go with those.

    However, among those who've just kept making things work for the past 15 years, Perl remains alive and well. It is still the fastest way to get the widest range of tasks done. And if you don't code like an obscurantist maniac, it's easy to maintain.

    It may look to us like Perl went away, but what really happened was an infusion of other people and trends. Now that the free money from a dot-com booming economy has gone away, Perl is shining through once again as the reliable and powerful option that it is.

    1. Re:Parallax by Eil · · Score: 1

      The market shifted. First, many Perl programmers shifted to PHP once the net decided security and economy of processing power were not goals on the table. Second, a lot of newer programmers are reliant on frameworks and other pre-built systems and learned the languages that go with those.

      Do you maintain the website linked as your home page? If so, what's it running under the hood?

    2. Re:Parallax by dolmen.fr · · Score: 1

      And you? Are you a Google fanboy because your homepage is hosted at Blogger?

    3. Re:Parallax by Anonymous Coward · · Score: 0

      Not obscurantist! ... Job security!

    4. Re:Parallax by Eil · · Score: 1

      As a matter of fact, I am.

  12. I remember when I turned 5.16... by Sez+Zero · · Score: 1

    Boy, a sweet five-16th birthday! Happy congratulations, Perl!

    So what to get a language for their 5.16th? A new Car-p? Or maybe an actual car from Dad's dealership?

  13. Perl's strength by Okian+Warrior · · Score: 5, Interesting

    Perl's strength is that it's expressive. It's not a language which is easy to learn or which generates heavily optimized code.

    In the demo phase, you're not really worried about performance. The goal is to have something showing as quickly as possible, and not worry too much about how fast it runs, or how much memory it takes. Overspec your demo system for the time being (ie - make it really fast and install lots of memory), and once you have a reasonable interface go back and recode it in a simpler language which can be more easily optimized.

    Languages which are simple to learn (c++, for example) are generally not very expressive. You end up wasting tons of time debugging issues of memory allocation, library interface details, and datatype conversion.

    Languages which are expressive are a little harder to learn, but any individual line in the expressive language does a lot more. Since you are writing fewer lines, and since the fewer lines do more, you end up making programs more easily and in less time.

    Yes, the programs will execute a little slower, but as mentioned, this is not important in the demo stage. Your productivity will be much higher.

    And there are lots of places where performance simply doesn't matter. Scripts usually fall into this category.

    Perl was written by a linguist, not an engineer. As such, it's harder to learn (it's got tons more keywords and context), but once you get the hang of it it's much more expressive. The following single line:

    @Lines = sort { $a->{Name} cmp $b->{Name} } @Lines;

    unfolds into several lines of C++, plus a subroutine definition with datatype definitions. The following line:

    @Files = <c:/Windows/*.exe>;

    can be implemented using one of over a dozen possible library calls in C++, but is builtin in perl. You don't have to look up the library call interface specific to your system.

    1. Re:Perl's strength by Anonymous Coward · · Score: 2, Interesting

      Well put. Except perhaps for the part about C++ being "easy" to learn. C++ is a fucking mess.

    2. Re:Perl's strength by Anonymous Coward · · Score: 1, Informative

      Perl was written by a linguist, not an engineer.

      And that engineer loved Latin, not Esperanto.

      The following single line:

      @Lines = sort { $a->{Name} cmp $b->{Name} } @Lines;

      In Python is:
      lines.sort(key=lambda o: o.name) # for inline sorting, or
      lines = sorted(lines, key=lambda o: o.name) # mimicking the perl idiom

      @Files = <c:/Windows/*.exe>;

      In Python is:
      from glob import glob
      files = glob("c:/Windows/*.exe")

      In other words, Python is just like Perl, only it is readable and makes sense.

    3. Re:Perl's strength by Anonymous Coward · · Score: 2, Insightful

      In other words, Python is just like Perl, only Python fans are deluded into thinking the Python way of doing things is the only viable way.

      Fixt.

    4. Re:Perl's strength by doti · · Score: 2, Insightful

      sorry, I tried many times to copy/past these so called python code, and then never work.

      yes, relying on white space is a stupid idea.

      --
      factor 966971: 966971
    5. Re:Perl's strength by Anonymous Coward · · Score: 1

      The fact that Python doesn't auto-glob is kind of retarded. The default should be to glob, and to provide a way to disable that if you have a good reason.

    6. Re:Perl's strength by skids · · Score: 3, Interesting

      In other words, Python is just like Perl, only it is readable and makes sense.

      Funny, I found the perl easier to read.

    7. Re:Perl's strength by Anonymous Coward · · Score: 0

      If you want expressive, check out the perl script at

      http://www.99-bottles-of-beer.net/language-perl-737.html

      The source code is an illustration of the output.

    8. Re:Perl's strength by Anonymous Coward · · Score: 1

      In Python is: lines.sort(key=lambda o: o.name) # for inline sorting, or

      What's lambda?

      In Python is: from glob import glob files = glob("c:/Windows/*.exe")

      It doesn't glob by default?

    9. Re:Perl's strength by Anonymous Coward · · Score: 0

      Both examples can be easily and beautifully done in a language which supports lambda expression and generator - and it would be more generic and readable, and allow even more complex operations than string handling.

      You can now do things in C# like that:
      var addUserCmds = Directory.GetFiles("C:/UserLists", "*.txt").SelectMany(file => File.ReadLines(file)).Select(line => pattern.Match(line).Groups).OrderBy(user => user["name"].Value).Select(user => new SqlCmd("insert into User values (@name, @age)", user["name"].Value, user["age"].Value))
      ExecuteAllCommandsInTransaction(conn, addUserCmds); // note the files are not actually read and parsed until ExecuteCmdsInTransaction finishes previous commands, during the entire process you'd not get things like an array of one million lines representing all the data

      it renders most script languages useless IMHO. You just have to write all the *shortcuts* first because there are very few official ones taking advantages of these new features.

    10. Re:Perl's strength by Anonymous Coward · · Score: 0

      Fix: the comment was wrong - OrderBy() would actually cause the pipeline to materialize into a List/array. You have to know all details for it to work smoothly, especially when it's complex...

      PS: My colleagues hate it when I write code like that

    11. Re:Perl's strength by Eil · · Score: 1

      Languages which are expressive are a little harder to learn, but any individual line in the expressive language does a lot more. Since you are writing fewer lines, and since the fewer lines do more, you end up making programs more easily and in less time.

      I'm not disagreeing with this in any way, but an expressive language which does a lot in a single line of code by definition means that it's harder for humans to read. And readbility is (in my opinion) directly proportional to maintainability. This is, perhaps, why Perl is sometimes derided as write-once, read never.

      I don't know if heard this maxim somewhere else, but I think it's pretty accurate: You'll never understand a line of code as clearly as the moment you write it.

    12. Re:Perl's strength by Anonymous Coward · · Score: 0

      In what universe does

      "lines = sorted(lines, key=lambda o: o.name)"

      come close to the obviousness of

      "@Lines = sort { $a->{Name} cmp $b->{Name} } @Lines;"

      Certainly not in this universe.

      Python is many things. Easier to comprehend than Perl? Not even close. It isn't.

    13. Re:Perl's strength by gullevek · · Score: 1

      Except that perl has an enormous amount of CPAN libraries that are often vast superior. Just take the perl interface to postgresql. No other language has such an perfect interface than perl.

      --
      "Freiheit ist immer auch die Freiheit des Andersdenkenden" - Rosa Luxemburg, 1871 - 1919
    14. Re:Perl's strength by Anonymous Coward · · Score: 0

      I'm not disagreeing with this in any way, but an expressive language which does a lot in a single line of code by definition means that it's harder for humans to read

      And a language which requires 100 times more lines of code to do something is easier to read? I think not.

      So the truth really is somewhere in between. You want enough conciseness so you don't have to keep scrolling around to actually read stuff so you can understand it. For that reason I often find verbose stuff like Java harder to understand - too often all the relevant lines don't fit the screen (and you have to also dig through X number of classes)...

      As for maintainability. There's another way you can write maintainable perl: where possible try to use decent modules from CPAN. That means less code is actually your code. That way some other experienced perl programmer has less to read, and when debugging they can skip a lot. Because they would know what the call to CPAN does, and if they didn't it's usually well documented. And the CPAN code often doesn't normally have to be documented or debugged by you. Yes there are bugs in the CPAN stuff, but the quality of the main stuff is usually better than average.

      Languages like LISP are great for completely "new ground" areas, where you need a language that is very powerful and expressive for all the code that you have to write.

      Languages like Perl are great because of all the code that you don't have to write. XML parsers, HTTP libraries, even DHCP packet parsing and creation etc.

      It is not as difficult to debug a car if someone doesn't keep reinventing the wheels and engines in weird ways.

    15. Re:Perl's strength by cheekyboy · · Score: 1

      slashdot is written in perl

      in todays i7's , perl runs as fast as P4.

      http://shootout.alioth.debian.org/u64/perl.php

      Sure, a mandolbrot may be way faster in java, but real world solutions, are not 100% math, but a combination of data transforms, logic and db acesss or rest access, with disk io or net io.

      And if most of your data is text, ie xml/json/csv, then perl can be as fast as java, but with less layers.

      --
      Liberty freedom are no1, not dicks in suits.
    16. Re:Perl's strength by Anonymous Coward · · Score: 0

      Just because you can put a lot on one line, does not mean you should. The strength of perl is that you can write something in many different ways. Personally I use this to make my code more readable. Yes you can write obfuscated perl, but you can write obfuscated python as well. A programmer who doesn't care about the programmers who come after him will always find ways to make code that can only be read by the compiler/interpreter.

    17. Re:Perl's strength by Anonymous Coward · · Score: 0

      PS: My colleagues hate it when I write code like that

      I'm not one of your colleagues and I hate it too. It's completely unreadable.

    18. Re:Perl's strength by Anonymous Coward · · Score: 0

      So did I

      Python doesn't look nice ever. (Like Cobol).

      I think anyone choosing python by choice is likely a boring and uninteresting person.

      (If it had any great advantages like really fast compiled code or it was fun to write or anything going for it then it might be ok)

      Go or any of the lisp dialects * or Haskell or Ocaml or perl are fun to write which is important.

      *(I have only experienced Common Lisp and Scheme but I expect the others are just as fun and given the opportunity i would certainly like to be able to try some others.)

    19. Re:Perl's strength by mzs · · Score: 1

      I agree and unless there's something in CPAN pretty much already solving my problem (which happens a lot actually), I almost always choose python so I'm being honest unlike that person that somehow thinks the python makes more sense. I think that with perl, it depends how much shell scripting someone did first. Somehow a person needs to have experience with some syntax that's not like C/java/pascal and has reached the limits of shell scripts plus tools like sed and awk first before perl clicks or they can see the value in it.

  14. Perl renaissance? by Fished · · Score: 2

    are we in the middle of a Perl renaissance?

    I hope not. I have to maintain a large body of Perl code at work, and it's a nightmare.

    --
    "He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
    1. Re:Perl renaissance? by kwoff · · Score: 5, Insightful

      Have you maintained any (large) body of code that isn't a nightmare?

    2. Re:Perl renaissance? by Anonymous Coward · · Score: 0

      are we in the middle of a Perl renaissance?

      I hope not. I have to maintain a large body of Perl code at work, and it's a nightmare.

      Perl Medic to the rescue!

    3. Re:Perl renaissance? by happy_place · · Score: 1

      I have to maintain a large body of legacy C code and guess what... It's also a nightmare. I love Perl. I use it daily to help me organize and maintain my archives, compare code, and manage it. Of course, I understand the language and have taken care to document the times I get overly idiomatic or use cryptic syntax, so that when I return to my perl scripts later, they aren't entirely unintelligible.

      --
      http://www.beanleafpress.com
    4. Re:Perl renaissance? by WebCowboy · · Score: 1

      are we in the middle of a Perl renaissance?

      I hope not. I have to maintain a large body of Perl code at work, and it's a nightmare.

      Funny that. I've had quite similar nightmares with Java and PHP, which are supposed to be all that. My history with Java has really REALLY put me off that languaage (and now with Oracle on the litigation warpath I've resolved to avoid Java whever reasonably possible--I'd even wipe my Galaxy S2 of the Java-esque Android and put on boot2gecko if the latter was really ready for prime time). In the case of PHP I found it to be like a walk in the pasture--an easy hike to start but then you step in a pile of crap and can't get that smell off of you. Perl, on the other hand, I learned in the mid-late nineties when I was tasked with authoring simple CGI scripts for an Apache web server on Linux, and I took to it fairly quickly and didn't get trapped in a nightmare. Perl certainly gives you opportunity to step in something smelly, but the simpe requirements in my situation didn't really invite that risk.

      Perhaps it isn't the language it is the authors (don't take offense if the large body of Perl you must maintain was written by yourself). I think my dislike of Java comes from the fact that for most of its existence it hasn't been used to do anything "fun". Java went all "enterprisey" and enterprise applications are just big slow stinky piles of anti-patterns. Maybe if I learned Java coding through programming games for Android phones instead of delving into the guts of some WebSphere appllication i would have thought different, but Android and mobile apps just didn't exist beyond what was hard coded into your dumb-phone. The nightmare isn't really Java itself, it's that it is most often used on "nightmare projects" driven by committees using stodgy old "waterfall" management methodologies, resulting in througly unpleasant software (for some reason enterprise software has to be wretched to use--if it isn't as slow, cumbersome and confusing to use as SAP then you aren't ready for production yet).

      I remember when PHP itself was a Perl library (how ironic is that, with so many people saying Perl is dead and you should move on to PHP or something like that?). I didn't give it a second look at the time because the PHP library didn't provide me with anything *I* needed at that point). Then somewhere along the line that was dropped in favour of a completely re-implemented "Perl-free" version that, well, looked and behaved like Perl's retarded little brother, and that didn't impress me much (but I DO understand that was probably why it caught on--less sophisticated--easier to adopt). Many years went by and PHP gained a lot of traction and got more complex and now I was confronted with the need to work with frameworks and content-management systems written in PHP. Guess what? PHP is not used to develop anything "fun" either--it is just un-fun in a different way than Java. Instead of dry, accountant-like programmer-analysts of the enterprise-Java world, you had freewheeling wunderkind "web developers" who churned out big balls of PHP goo floating in HTML tag soup. No anti-patterns here--no discernable software design patterns at all actually. And it seems that PHP develpers were the slowest learning programmers of the entire world--even after VB6 devs were refactoring their "code" to implement paramaterised ADO queries it seems PHP devs happily continued to cobble together un-escaped strings and inviting little Bobby Tables to own their arses. When I eventually delved into the guts of the likes of PHPbb and Wordpress and Drupal modules I felt a bit like PHP was in over its head--constantly being called upon to do just a bit more than it was designed to do and that PHP was continually catching up.

      I know that Perl is no better--I'm sure that there are critical enterprise systems out there supported by crufty, cryptic Perl that looks like line noise. I'm sure someone out there could cite SQL Ledge

  15. Re:erm by X0563511 · · Score: 1

    I think you replied to the wrong story.

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  16. Re:Renaissance? by budgenator · · Score: 1

    Who said anything about dagos and cathedrals? That's a bazaar inference!

    Well played Sir, well played indeed!

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  17. calls C/C++ libraries by bzipitidoo · · Score: 3, Interesting

    Ultimate glue? That's why I'm interested in Perl 6. It's supposed to be able call C/C++ library functions directly. No more need for wrapper libraries, which is the majority of CPAN. No need for SWIG, which I find bloated.

    --
    Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
  18. There will be no Perl renaissance by Anonymous Coward · · Score: 0

    Sorry, Perl fanboys, but Perl is dead. Not only has it been eclipsed in the web domain by PHP, J2EE, ASP.Net, Ruby on Rails, and others, but in the scripting domain it has been overtaken by Python. Perl's mindshare has plummeted in the last 10 years or so, and it's only going to get worse as all the new CS grads are much more interested in functional languages, e.g. Haskell; to these people Perl seems like an example of terrible language design. Perl more and more appears to be used mostly by some old neckbeard diehards who haven't kept up with recent developments in programming.

    So yeah, of course some people are still using Perl, just as some people are still using Tcl. But overall you can stick a fork in it; Perl's dead.

    1. Re:There will be no Perl renaissance by chromatic · · Score: 2

      So yeah, of course some people are still using Perl....

      We call that the CPAN, and it's the opposite of plummeted.

    2. Re:There will be no Perl renaissance by Anonymous Coward · · Score: 0

      Wow, talk about being in denial...

    3. Re:There will be no Perl renaissance by chromatic · · Score: 1

      If you're interested in facts, feel free to provide measurements or statistics to prove me wrong.

    4. Re:There will be no Perl renaissance by Sez+Zero · · Score: 4, Informative

      Sorry, Perl fanboys, but Perl is dead. Not only has it been eclipsed in the web domain by PHP, J2EE, ASP.Net, Ruby on Rails, and others, but in the scripting domain it has been overtaken by Python.

      TIOBE Index seems to disagree: Java, C#, PHP, Python, Ruby all down.

      Perl right there at 9, same as it ever was: a good tool for people that want to get work done and not chase the hot flavor of the month.

    5. Re:There will be no Perl renaissance by rubycodez · · Score: 0

      Facts? what widely used "new" project in the last five years has chosen Perl? there are plenty of examples for Python, Ruby, Java/J2EE, Objective C, C, C++, C Sharp.....but Perl is dying. Larry killed it wasting his people's cycles with Perl6. Perl is washed up, a has-used, used-to-was. RIP Perl.

    6. Re:There will be no Perl renaissance by rubycodez · · Score: 0

      Haha, from search engine rankings? that's just annoyed people having to look up old crud. Get over it, Perl is dying, its corpse is stinking. Larry killed it.

    7. Re:There will be no Perl renaissance by chromatic · · Score: 1

      ... what widely used "new" project in the last five years has chosen Perl?

      I've deployed a few projects in the last five years. I know many people who've also deployed projects.

    8. Re:There will be no Perl renaissance by Anonymous Coward · · Score: 0

      duckduckgo.com is just one that pops into my mind http://duckduckgo.com/traffic.html

    9. Re:There will be no Perl renaissance by Anonymous Coward · · Score: 0

      What else? Any ranking will involve results from search engine.
      I've looked at several sources including the TIOBE index and the Transparent Language Popularity Index.

      While Perl is on slow decline, it still has 2x market share than Ruby.

    10. Re:There will be no Perl renaissance by rubycodez · · Score: 1

      there are plenty of useful sources other than search engines. firms who hire and employ software developers are given surveys, for example. Perl developer "share" is in huge decline. At no place I've worked in (huge clients with thousands of employees) in the past ten years was there a Perl developer. C, C++, Visual Basic, Java, Python, Ruby, even COBOL.....but no Perl. Unlike the 90s

    11. Re:There will be no Perl renaissance by rubycodez · · Score: 1

      yes, that's a valid point, forgot about that one. exception that proves the rule, I'd say

    12. Re:There will be no Perl renaissance by Anonymous Coward · · Score: 0

      Sure, but even the job postings show a lot of requirements with "perl" in it, even today.
      http://www.indeed.com/jobanalytics/jobtrends?q=perl%2Cpython%2Cphp%2Cruby&l=

      I think Perl is still around and relevant in the scripting language field. I just wish Perl 6 came out sooner, as Perl's suffering the Perl 6 vs Perl 5 divide much like Python 3 and Python 2 -- except that Perl's been ongoing for 10 years now. This divide has been hurting the language for sure.

  19. Bunch of stuck up nannies by cheekyboy · · Score: 5, Insightful

    If they write their own code, its unreadable?

    Fire them.

    Its easy to write code in perl that looks like C and is readable, and still fast. (Often faster than java btw)

    Yes, using shortcuts and lots of login in one line is cute, but its horrible to read, so DONT do it.

    --
    Liberty freedom are no1, not dicks in suits.
    1. Re:Bunch of stuck up nannies by SpaghettiPattern · · Score: 1

      Yes, using shortcuts and lots of login in one line is cute, but its horrible to read, so DONT do it.

      Once I met an absolute bastard in the Perl community, sneering at my code because every module was documented. The cheerful dogma "it was hard to write, it should be hard to read" still lingers. Gives you the same demoralising feeling as middle-managers stating that "If it's that easy to understand it must have been dead easy to develop."

      --

      I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
    2. Re:Bunch of stuck up nannies by Anonymous Coward · · Score: 0

      (Often faster than java btw)

      That's not really saying much, is it?

  20. Yea Perl by Anonymous Coward · · Score: 0

    I love Perl. For quick tasks, utilities, parsers, code generators..etc have no idea what I would do without it. Actually I know I would be wasting much more of my employers time writing this shit in a different language and most likely would just choose to do a lot more shit work manually with increased chance of errors and less automation.

    I get to get away with taking shortcuts that would not be advisable in a large project for pennies on the dollar. As much as I love Perl I'm not sure I would trust myself enough to use it in a huge project unless I forced myself not to use certain features.

  21. Re:Your sig by bill_mcgonigle · · Score: 1

    Check out what lack of religion did to the Soviet Union, China, Vietnam, Cambodia, Cuba, and others.

    No doubt totalitarian socialism had nothing to do with their outcomes, though.

    (an all-powerful State can't tolerate any parallel power structures, such as a Church)

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  22. Many reasons to use Perl by Anonymous Coward · · Score: 1

    I can think of over 106,000 reasons to use Perl (and by the way, CPAN is still seeing very large numbers of both contributions and contributors).
         

  23. Ruby TYVM by Anonymous Coward · · Score: 0

    I used to hack a lot of perl4 then perl5. Then someone invented Ruby. RIP perl.

    Perl6 looks similarly cool -- maybe my descendants can hack it someday.

  24. Re:Your sig by Anonymous Coward · · Score: 0

    Communism was their religion. State mandated.

  25. Perl needs a PR makeover by Anonymous Coward · · Score: 0

    Many of us like Perl. We all know how faddish the industry is about languages and tools. Remember the Rails hype. And how Python suddenly was "cool". Ok so nobody cares anymore if Perl6 surfaces or not and certainly no-one wants to learn a whole set of new Perl syntax (Perl5 is hard enough for most it seems, although I never found elementary Perl all that hard - there are so many snippet examples around).

    What Perl needs is re-hyping so that all our pimply-faced younger brethren entering the industry, most of whom have probably never played with Perl, decide that Perl is uber cool, rock solid, add hyperbole here. Maybe big-bucks development competitions pitting a skilled Python team against a skilled Perl team for example? A PR campaign directed at coder websites, Slashdot etc. Something like that?

  26. Perl is actually 'another' language by hughbar · · Score: 1

    I've been using Perl on small and big projects [both my own and commercial] since about 1994 and am very aware of its defects, terse and sometimes confusing syntax, especially 'things that work but somewhat unexpectedly', weak typing unless you add module magic etc. etc.

    However, it has always felt incredibly intuitive and efficient, because, I suspect, that a linguistics person rather than a hard-IT construct-elegance person is behind its design. That and the fact that you can find a library for anything you want on CPAN, a good thing and a bad thing means that it remains my language of choice.

    Natural languages are messy but expressive, intuitive and efficient, with a downside of [for example] some ambiguity, there's no reason not to try this a programming language. As I said in another post, I'm not sure I'd use Perl for avionics though.

    --
    On y va, qui mal y pense!
  27. Re:Your sig by Sique · · Score: 0

    10^-43 seconds after the Big Bang, today's universe's physical laws were in place and have never changed since. That means that God lost interest in his creation about 0.000,000,000,000,000,000,000,000,000,000,000,000,000,000,1 seconds after he started to create. Talk about ADS!
    Or to put it mildly: One can talk about his moral flexibility, jealousy, short tempered manner, righteousness, self aggrandising and recklessness, but the real complaint is that he wasted so much of his talent.

    (Shamelessly stolen from Vince Ebert.)

    --
    .sig: Sique *sigh*
  28. Awesome by mattr · · Score: 1

    From the link:

    According to the developers there are 590,000 lines of changes across 2,500 files from 139 authors in Perl5.16.0. Perl5.16.1 should be published on 20 June, addressing any significant bugs found in the 5.16.0 release. Work will then begin on the 5.17 development branch which should arrive as Perl5.18 in May next year. /blockquote?
    Sounds like a HUGE amount of development! I had no idea of the scale of the effort and love and use Perl myself.
    Hard to imagine how anyone intelligent could ever say Perl is not timely with this kind of mass coordination going on. (Not to mention Slashdot being written in Perl IIRC...)
    Personally I am excited about the Modern Perl book (I seem to have self-censored myself into using older versions).
    I have used and liked Catalyst but have also imagined even easier ways to build systems with it and say Moose.
    So I am going to have a lot of fun trying out Dancer and PSGI/Plack.

  29. Awesome (2nd try) by mattr · · Score: 3, Insightful

    From the link:

    According to the developers there are 590,000 lines of changes across 2,500 files from 139 authors in Perl5.16.0. Perl5.16.1 should be published on 20 June, addressing any significant bugs found in the 5.16.0 release. Work will then begin on the 5.17 development branch which should arrive as Perl5.18 in May next year.

    Sounds like a HUGE amount of development! I had no idea of the scale of the effort and love and use Perl myself.
    Hard to imagine how anyone intelligent could ever say Perl is not timely with this kind of mass coordination going on. (Not to mention Slashdot being written in Perl IIRC...)

    Personally I am excited about the Modern Perl book (I seem to have self-censored myself into using older versions).
    I have used and liked Catalyst but have also imagined even easier ways to build systems with it and say Moose.
    So I am going to have a lot of fun trying out Dancer and PSGI/Plack.

  30. So: how to sell Perl? by Anonymous Coward · · Score: 0

    So how do Perl lovers (I'm one but an amateur) pitch using Perl to the unbelievers? How to defeat all the cliches about Perl and the Python dinky toy fanboys? How to convince management (who know less than an amateur anyway)?

    I, for one, want Perl to fight back and win. I enjoy writing Perl and wouldn't mind turning it into an income stream sometime. I also think I don't need to be 13yo and have an IQ of 190 to write useful Perl, it works well for us older guys.

    1. Re:So: how to sell Perl? by mattr · · Score: 1

      I always try to write a lot of comments into my code, whatever the language.
      Most sample code and tutorials do so too.
      So I would say, why not post some real world programs in Perl and Python and let people see what they look like, including comments. Even in this thread I see people talking about line noise but frankly, I don't see it. There are a lot of things I don't use in regexes for example but I know it can be done and if I want to I can always perldoc on the command line and brush up on what I don't remember or do so on the web. Since I don't know python much compared to perl it may just be me but my impression is that such comments come from people who have not taken the trouble to learn perl. I mean, there is no line noise in my programs and I split things into several lines and make it look pretty to keep my mind straight, beyond what is needed perhaps. It is possible to develop your own writing style in Perl whereas Python is apparently stricter, but there is probably a bit of missing information in both camps about what it is like in reality to program in the other side's environment.

  31. Re:Your sig by Anonymous Coward · · Score: 0

    You think people who post stuff like

    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger

    aren't actually behaving just like those religious freaks too?

    You take away religion from people and they'll find another one. Whether it is a hockey team or State Atheism or Environmentalism or whatever, and then proceed to use it as an excuse to attack or even kill hated people.

  32. Re:Your sig by INowRegretThesePosts · · Score: 0

    Check out what lack of religion did to the Soviet Union, China, Vietnam, Cambodia, Cuba, and others.

    No doubt totalitarian socialism had nothing to do with their outcomes, though.

    (an all-powerful State can't tolerate any parallel power structures, such as a Church)

    But Marxist Socialism is caused by the very same doctrine that today is advanced by Richard Dawkins.
    The ideology if Richard Dawkins has at least two tenets:
    1) Materialism - that is, reality (including the human mind) can be explained by the laws of Physics (see http://richarddawkins.net/articles/490048-the-blue-brain-blues-materialist-ethics-and-simulated-minds)
    2) Anti-religious intolerance: religion is irrational, superstitious and must not be tolerated. It must be wiped out. While it still exists, it must be contained to the private sphere - that is, the political rights of people of faith must be curtailed.

    And these two tenets are at the core of Marxism. Marx took the idea of materialism and developed it into his "materialistic conception of History", which is the root of Marxism. And he fully incorporated anti-religious hatred.

    Therefore, the ideology of Dawkins (which of course existed centuries before Dawkins) is a clear cause of Marxism, and therefore 100,000,000 deaths, torture, general suffering, terror, repression, censorship, bigotry and societal decay.

    In other words, Dawkins is the *last* person that can complain about the "evils" of religion.

    There is a wise analysis about the ideal relationship between state and Church, which must be balanced to avoid oppression. See http://www.lewrockwell.com/orig6/ratzinger2.html (Why Church and State Must Be Separate, by Benedict XVI)

  33. Re:Your sig by INowRegretThesePosts · · Score: 1

    Flamebait?! I was responding to the signature of the grandparent! Do moderators know any impartiality?

  34. Re:Your sig by Anonymous Coward · · Score: 0

    TL;DR: Dawkins killed 100 million! (Hey, if you can misread posts, so can I!)

    Very few of those deaths have to do with anti-religious intorlerance and none with materialism. Marxist socialism doesn't imply totalitarian socialism. But, hey, doesn't it feel great to be winning, even if you're just kicking down a strawman you built yourself?

  35. Re:Your sig by INowRegretThesePosts · · Score: 1

    TL;DR: Dawkins killed 100 million! (Hey, if you can misread posts, so can I!)

    You deliberately misread what I said. This suggest you have no argument and decided to resort to fallacies.

    Very few of those deaths have to do with anti-religious intorlerance and none with materialism. Marxist socialism doesn't imply totalitarian socialism.

    What? Have you ever studied Marxism? Marxism explicitly advocates class hatred, violent revolutions and the dictatorship of the proletariat.

    Please at least attempt to argue rationally.

  36. Re:Your sig by Anonymous Coward · · Score: 0

    You deliberately misread what I said. This suggest you have no argument and decided to resort to fallacies.

    Exactly, exactly! That was my point. Could you please get a better mirror? You seem to not notice that log in your own eye.

    Have you ever studied Marxism? Marxism explicitly advocates class hatred, violent revolutions and the dictatorship of the proletariat.

    Have you? You still seem to be speaking about brand of socialism practised by USSR and other totalitarian states, not about marxism.

    For a start, you seem to be misunderstanding what does "dictatorship of proletariat" mean.

    Could you also provide some quotes from Marx about _violent_ revolution, class hatred, and how it necessitates oppresive totalitarian regime and 100,000,000 deaths?

    And, lastly, what does it ever have to do with Dawkins?

  37. Re:Your sig by Anonymous Coward · · Score: 0

    Flamebait?! I was responding to the signature of the grandparent! Do moderators know any impartiality?
    --
    Claiming one will be modded down because "Slashdot" is biased against one's idea is often a cheap way to be modded up.

    And now you seem to be responding to your own signature.

  38. Re:Your sig by bill_mcgonigle · · Score: 1

    But Marxist Socialism is caused by the very same doctrine that today is advanced by Richard Dawkins.

    Let's assume that's correct. Dawkins is an atheist and he promotes violence to achieve his social ends (socialism). I don't know if that's true, but it doesn't matter.

    There are many non-theists who advocate and live by the non-aggression principle, Satyagraha, or Jesus's non-violent teachings. So you can make a 2x2 matrix of theists/atheists (x,y) and people who do/don't (m,n) support violence as their means.

    You clearly have a problem with States in the (y,m) quadrant. That's great. Personally, I have a problem with States in the (m) half, but then again, all States are in the m half by definition. My rather non-simple conceptions about our Universe's purpose and creation aren't relevant to that judgment, but any follower of Jesus, for example, should be aligned in the (n) half and work to convince the (y) half, but far too many buy into later corruption of his teachings (designed to bolster State power) and support the (x,m) quadrants wholeheartedly.

    If you have theists who actively work against their Gods' teachings, what matter is it that they are theists if it's not relevant as cause of their actions?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  39. Re:Your sig by Anonymous Coward · · Score: 0

    Wrong; my signature criticizes posts with "now watch as I will be modded down by Apple fanboys", in which a pre-declaration of victimhood ends up having the opposite effect, even though the poster has no reason to feel victim.
    But in my case, a moderator actually modded me "flamebait" with no possible justification.

  40. Re:Your sig by INowRegretThesePosts · · Score: 1

    First, I didn't mean that Dawkins explicitly advocates violence; I merely say that his ideology, if it spreads, will eventually lead to great violence.

    I agree that people who believe in Jesus should live by His teachings. And regarding state-sponsored violence, please check out www.lewrockwell.com/orig6/ratzinger2.html (Why the Church and state must be separate, by Pope Benedict XVI).

    And just so you know where I am coming from, i am half-conservative and half-libertarian. I am pro-life, anti-war, pro-immigration, pro-small government. I am even open to the idea of legalizing some recreational drugs (I think they are evil; but not every sin must be a crime).

    My original point is simply that Dawkins is extremely partial and intellectually dishonest. He spreads the idea that religion is pure evil and that we must be hard-core materialists and be a huge intolerant impolite dick to anyone who believes in God. I am merely saying that this is wrong.

    Regards

  41. Re:Your sig by robsku · · Score: 1

    There was never lack of religion, you are talking of the attempt to deny religions which, while it lasted, did a lot of bad, but I'm not sure what exactly do you think it did... but I'm guessing that you are assuming too much as usually when I hear something like this it seems that the person is associating intolerance for religion with all things that did go bad + all things that they think went bad - and often also ignore that not all socialist / communist (so called...) countries even try to kill religion and even that most of those that did also eventually gave up and realized that it was a futile attempt anyway.

    Yes, it was really bad and I have no respect for what evil has resulted of religious intolerance (inflicted by anyone, including hatred against other religions and hatred against atheism). And no, I don't even know what exactly are you suggesting, the above assumptions are just that and what I really ask is to explain yourself - I'm not blaming you for anything in my text above, I can't, from what little you wrote, have knowledge of your personal views and what exactly you meant.

    --
    In capitalist USA corporations control the government.
  42. ...jokes about perl being unreadable... by robsku · · Score: 1

    ...jokes about perl being unreadable are childish and I usually tell such people to learn perl or shut up, because basing your knowledge on perl 4, one-liners for CLI & obfuscated perl contests does not give very professional image of their programming knowledge.

    --
    In capitalist USA corporations control the government.
  43. Re:Your sig by INowRegretThesePosts · · Score: 1

    Troll!?
    Mods, have some honesty please!
    "Troll" is not a substitute for "I disagree".