6 ms·
Perl 5 has nothing to do with Perl 6 development or even releases. Even after Perl 6 is released Perl 5 will still continue to evolve and grow. At the moment P
by kamaal 15y ago
Perl 5 has nothing to do with Perl 6 development or even releases. Even after Perl 6 is released Perl 5 will still continue to evolve and grow.
At the moment Perl 6 specification gives a good evolution map for Perl 5 development. So you need not to have to ever worry about Perl 6.
Perl 5 is a solid language in itself. Perl has been amazingly useful since almost 25 years now. And anybody who denies this is simply trolling. Its useful for almost anything to everything. From scripting, to application development, to prototyping to building reliable applications in any domain.
Perl adapts to nearly every programming paradigm out there. Object oriented, functional, declarative you say it Perl has it. Its amazingly flexible, easy to learn and extensible.
You also get to benefit from the community experience and knowledge accumulated over years. You get the power of CPAN. There are also amazing resources to learn Perl.
Its a tool that you will never stop being in love with.
Those of us who have used Perl and pushed its boundaries to get amazing stuff done over years, even now can't write down words to describe its greatness. We can only tell you how great it is, but when you see it yourself you will know it.
But the position of any new Perl programmer is enviable to say at the least. He stands at the gates of a city which is going to take him to places he has never seen and experiences he has never been through. Most of them are going to change his life for ever.
- creamyhorror 15y agoI have hardly ever seen such high praise for a language. I guess I'll have to learn it sometime and see what the hoopla's about. With the Modern Perl book, of course, if it's still the best-of-breed then.
- bgilroy26 15y agoIf you enjoy Modern Perl, check out Higher Order Perl. It's a guide to functional programming in Perl and it's full of hipster-programmery goodness!
- kamaal 15y agoOne way to measure the utility of a language is to see how its users perceive it. Both in the times of technology hype and otherwise. If I look at the Java world, I see most programmers come there because they need a job. I would program in Perl even if I would not be paid for it, just for the fun of it. Its like painting, or playing the piano, or drinking fine wine. I would like to do them, even there is no direct benefit from them. Some languages get a special distinction that its users just love to program in it. Languages and tools like Lisp, C, Perl, Vi, Emacs etc they just never go away. Because someone somewhere is always discovering some goodness in them and is using it. And that process is timeless. These languages have managed to last for decades sometimes their adoption drops, sometimes it peaks, sometimes there is a constant line of usage. But they don't go away. If you read the mailing lists during early days of Perl on comp.lang.perl.* and other writings by people like Tom Christiansen. You will see some unique tone of passion and excitement. The golf competitions, the discussions on one liners, the growth of CPAN, the occasional gems posted on Perl Monks. Great books like Programming Perl, Higher Order Perl and Modern Perl Book and Perl's extreme practical approach and emphasis of 'Getting things done'. I guess for people on Unix platforms who had no other respite but to use C and a mash of other Unix text processing utilities. Or for Java programmers who have to write 10 classes to open a file and do trivial operations. Perl is almost like giving Ice water to somebody in hell.
- read_wharf 15y agoAlthough Python is taking more of these roles over time, Perl is still the thing that holds much of the internet's infrastructure and tools together, as well as internal servers, so it's a good thing to know if you're interested in all that.
- kamaal 15y agoHmmm, Python has some great frameworks and is a great language. But unfortunately, its almost like going backwards. Perl was invented because C + Unix text processing utilities together were not proving to be good for many tasks like Text processing, fast prototyping etc. Now using another C based language which doesn't do that, takes us back to the old problem again. IMO, Python doesn't solve those problems. Regex support is really bad in Python and file operations are not trivial. There is too much of Java feel to it and it just doesn't have the feel of bash/perl/awk's scripting powers. Scoping is just not right. There doesn't seem to be a sane ways of evolution without breaking backwards compatibility. No equivalent of CPAN. And in many ways white space based parsing is not good for large and nested code blocks. It still doesn't have multiline lambda's. And its too much do-it-one-true-way kind of language, that sort of is a blocker for quick hacking. Because I like to write what I think, and not the other way around. The language is too verbose, and unlike Perl and Emacs there are no exponential productivity gains over time. But I agree though, that Python does have some other good things. The OO syntax is neat, there are some great frameworks like Twisted and Django. And there is low barrier to entry which makes new bie feel just at home. The tutorials are just too good. And good standard libraries ship with it.
- overgard 15y agoWhat you're saying seems handwavey and imprecise. What -- specifically -- is wrong with regular expressions and file operations in python? How is white space parsing "not good" for large and nested code blocks? (And why do you have large nested code blocks in the first place? Break those up! Those are hard to read regardless!) And how is there a "java feel"? What does that even mean? And in what way is python verbose? In my experience almost everything about it is almost as terse as possible, from the lack of needing curly braces to the minimalist syntax to naming things like "str" instead of "string"
- danssig 15y agoThere is no hoopla outside of the echo chamber. If you want a truly amazing language I would suggest things like Haskell, Racket, Clojure, Erlang, Smalltalk, and/or Common Lisp. If you're looking for more batteries included then I'd suggest Python or perhaps Ruby. Things are always going on in those communities and they've made some great killer apps like Blender (python), Rails (Ruby), Django (Python) and countless more. These languages are just as flexible as Perl, though they have their strengths and weaknesses in different places than Perl does.
- stcredzero 15y agoObject oriented, functional, declarative you say it Perl has it. Its amazingly flexible, easy to learn and extensible. My first programming job was in Perl back in the late 90's. Loved it, but I have to say that the OO facilities left something to be desired. I found them fatiguing. It took Java, then Smalltalk for me to really get OO. Perl requires too much mastery of mechanism just to do objects, so it's not the best environment for learning OO.
- chromatic 15y agoMy history is the opposite. I failed to understand objects in C++, then learned Java, and then learned Perl. Playing with the mechanism helped me understand OO. (Exploring Smalltalk after that helped.) After learning Moose a couple of years ago, I don't miss the Perl 5 mechanism at all.
- jrockway 15y agoI agree with chromatic below; Java and C++ do not teach you OO. They teach you cut-n-paste without a text editor. (When Bar extends Foo, you're copying-and-pasting Foo's code into Bar, and then tweaking it. Or at least that's how class-based OO is used a good percentage of the time.) A better way to program is with interfaces and composition via delegation, something that Java and C++ support but have no syntax for making it easy. Perl's Moose object system, on the other hand, has easy support for composition via roles and delegation via ... well, delegation :) And, you have "extends"-style OO available if you think it's the right solution to a particular problem. So really, I think it's a fine way to learn OO. Doing things right is easier, if you decide to do them right. (We do Java OO right at Google, but it sure involves a lot of typing and @hacky-attributes. And I've never seen good Java OO anywhere else.)
- stcredzero 15y agoAs a Smalltalker with a decade of experience, I too find Java a bit lacking. That said, it was a better environment for OO than Perl at the time. I was able to get a feel for refactoring through Java, though. That primed me for Smalltalk and the joy of no primitive types.
- danssig 15y agoI don't generally see sales pitches of this level on sites actually selling something. >And anybody who denies this is simply trolling. Logical fallacy: Appeal to emotion. "My argument cannot be argued with because " is always a logical fallacy. "amazingly useful" is subjective, so of course it can be argued and doing so is not trolling but perfectly reasonable. Don't make claims you don't wish to back up. >Its useful for almost anything to everything. From scripting, to application development, to prototyping to building reliable applications in any domain. Logical fallacy: Misleading vividness. While what you say may be true, you've just described a programming language. There is nothing in this sales pitch that is perl specific. >Perl adapts to nearly every programming paradigm out there. This one is a better claim. The proper term is "multi-paradigm". Most (all?) Lisp dialects are also multi-paradigm, among various other languages. >Its amazingly flexible, easy to learn and extensible. "Amazingly flexible" is subjective. For example, a Smalltalk or Lisp programmer isn't going to be impressed (nor would programmers of Self, IO, etc., etc.). Easy to learn can be tested to some degree and I believe you'll find the data against you. It would be an interesting to catalog the kinds of questions that get asked about the various languages. In my anecdotal experience, people start having problems with perl right at the beginning with e.g. how variables work. Extensible is again "Misleading vividness". I can think of more languages that have a similar level of extensibility than those that do not. >You also get to benefit from the community experience and knowledge accumulated over years. Misleading vividness. >You get the power of CPAN. Overemphasized. Use a JVM-language (e.g. Clojure), for example, and you'll get the power of any open source JVM-language code ever written. >There are also amazing resources to learn Perl. Again, if you look at popular languages today there are few that wouldn't tick this box. >Its a tool that you will never stop being in love with. This claim is just ridiculous and wrong. I used perl professionally for over half a decade. At first I didn't care that much one way or the other. I was a C++ programmer and this was easier in some cases (but less flexible in other ways that I was used to exploiting). But as the years went on I grew to hate the language more and more until I just couldn't bare it anymore. I hated the backwards defaults (e.g. dynamic variables are fantastic. But as a default? wtf?), how ugly sigils look in code, the embarrassing "OO" syntax at the time and, one of the worst, how the community was constantly trying to prove they were relevant (obviously still the case). You could never mention Perl online or around Perl people without having to listen to the same tired tautologies about how incredibly powerful it is (wtf have you been using to think this?), etc. So no, it's not a tool you'll never stop being in love with. This is the "Mind projection fallacy". You feel that way, but the vast sea of perl developers who abandoned ship for Python, Ruby, PHP, etc. obviously don't. >Those of us who have used Perl and pushed its boundaries to get amazing stuff done over years, even now can't write down words to describe its greatness. More "Misleading vividness". We all have stories like this in our favorite languages, but practitioners of other languages don't seem to feel compelled to post them anywhere and everywhere. >We can only tell you how great it is, but when you see it yourself you will know it. Appeal to mysticism. Sure we will. >But the position of any new Perl programmer is enviable to say at the least. Hah! If you had just said "Programmer" I would have found this an inspiring sentiment, but Perl programmer? No. I don't envy several months of "wtf" (e.g. the first time you figure out that your code accidentally applies ++ to a var that has a string in it and instead of crashing so you detect this immediately it does something with it).