49 ms·
Is Perl 6 Being Renamed?
- adamnemecek 7y agoI'm not surprised that the language is dying. They seem to be spending time on things no one cares about and things that are inconsequential.
- 83457 7y agoAny examples?
- liveoneggs 7y agothe name is the example
- roryrjb 7y agoCould it be that the Perl language (and especially Perl 5) but as a community in general, is established and mature, and very stable, that the only things that are mentioned are just not the things that newer, fast moving languages such as Rust and Go talk about? I don't think that the naming situation is trivial, I really think it has had a negative effect on both Perl 5 and Perl 6.
- coldtea 7y ago>Could it be that the Perl language (and especially Perl 5) but as a community in general, is established and mature, and very stable No, it's also declining. If not for anything else, because most younger devs won't touch it (either 5 or 6).
- jerf 7y agoThis is by far the most important thing they could be doing right now. It should have been done 10-15 years ago, and is arguably the dominant remaining reason for why the work done on both Perls since Perl 6 has failed to payoff the way it should have. There is a certain contingent of developers who should have been all over Perl 6 and very excited about it. We should have been seeing the stream of "$COMMON_LIBRARY but in Perl 6!" postings on HN for a couple of years, along with the blog posts of "look how crap this is to write in $OTHER_LANGUAGE but with this bit here and there look at how slick the Perl 6 solution is!" every couple of weeks. We should be seeing blog posts about the joys of working in a language with built-in grammar support replacing the old ad-hoc regex support, and how well it integrates with the rest of the features. We should have even eventually seen the contrarian backlash posts about how much of a mess you can make if you overload all your operators and grammar constructs and use all the features at once in an ill-advised manner, followed by comment thread semi-flamewars about whether bad code is the fault of the programmer or the language. But we didn't. Bias disclosure: I actually have no interest in Perl 6, so this isn't advocacy. Anything I've ever seen that Perl 6 looks interesting to me (emphasis) for, I'd rather just use Haskell, which I've already learned and actually does quite a lot of what Perl 6 does. But Perl 6 does it without being a immutable functional programming language, making this all a lot more accessible to a lot of programmers. I'm not saying I'm interested in Perl 6; I'm saying, there is definitely a chunk of programmers who should have been interested in it who are not. And from what I can see, this naming confusion is one of the major reasons. (One other one I would point to is the Perl 6 community's multi-year "joke" that Perl 6 would be released "next Christmas", which nobody outside of the Perl 6 community found even slightly funny, instead creating a reputation for the community that overpromises and underdelivers; that a few people would swoop in to those conversations to actually mock people who weren't insiders enough to know it was a joke and not a real promise, which is to say, 99.9999999% of humanity (that is not random nines; that is all but ~700 people; take one off if you like), really didn't help. I put "remaining reason" in my first paragraph because this has been resolved for many years now. But I can tell you that this significantly diminished my own personal interest, and I'm sure I'm not alone. Finally, I'd point to it just never being done, but, arguably, that alone couldn't have killed it. There's plenty of languages that grow quite substantially over time; the Python of when Python first really got popular and the Python of today are very different, for instance. Had more people been interested and pushing for something usable $TODAY, with more work being done later, this probably wouldn't have been as big a deal.)
- DonHopkins 7y agoI believe Perl 5's decline and Perl 6's failure to catch on is evidence of the failure of their common underlying TMTOWTDI philosophy, which encourages write-only "creative snowflake" Perl code that's an inscrutable, unreadable, unmaintainable nightmare. (The sigil-heavy line-noise syntax sure doesn't help, either.) https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to_do_it https://en.wikipedia.org/wiki/There%27s_more_than_one_way_to... http://wiki.c2.com/?ThereIsMoreThanOneWayToDoIt http://wiki.c2.com/?ThereIsMoreThanOneWayToDoIt While I believe Python's continuing success is evidence supporting the truth of its Zen of Python philosophy: "There should be one — and preferably only one — obvious way to do it." https://www.python.org/dev/peps/pep-0020/ https://www.python.org/dev/peps/pep-0020/
- jerf 7y agoSo I basically agree with you & jschwartzi. But to expand or reinforce my original point, it is very clear there is a substantial contingent of programmers who do not. While of course in my own opinion, my own opinion is correct (duh), at a more global level, or maybe in a more academic sense, I'm open to the possibility that I'm wrong. I've already flopped on that matter once in my career and I reserve the right to be convinced by another language that I'm wrong now, too.
- Qcombinator 7y agoYou don't have to be "wrong". You just have to be not exactly the same as everybody else. And of course, nobody is exactly the same as everybody else, therefore there is not possible for there to be such a thing as The One Perfect Language. The right tool for the job; but also the right tool for the workman.
- alabamenhu 7y agoThe idea that there's only one way implies that code context means nothing. For example, if you have a simple function that kicks backed cached values: sub foo ($bar) { if %cache{$bar}.defined { return %cache{$bar} } } Is an absolutely correct way of doing things. But it's messier then using a postfix: sub foo ($bar) { return %cache{$bar} if %cache{$bar}.defined } Or simplifying: sub foo ($bar) { return $_ with %cache{$bar} } While it's true that sub foo ($bar) { .return with %cache{$bar} } is possible, I don't tend to use it too much because the dot syntax isn't as pretty with postfixes ha. But each of these options has a place where it is the better option, but none of them is universally the one and only best option. Nested ifs with multiple statements may go better with the first one, but if several conditionals have similar elements and are simple statements it might behoove to line them up with whitespace. But the placement of return right at the outset (as opposed to nestled in an if statement) to me makes it clear the return value is a gate-keeper of sorts. Ditto for using 'die if [cond]' which much more in your face then 'if [cond] {die}'. All of the above code is readable though. Of course, a functional approach could be just as valid and readable, and clear: multi sub foo ($bar where %cache{$bar}.defined) { %cache{$bar} } multi sub foo ($bar) { ... } Or taking advantage of traits: sub foo ($bar) is cached { ... } Almost inevitably the unreadable code is where someone is trying intentionally to be cute and write unreadable code. But that can be done in languages like C too, or with any language that allows single letter variables.
- roryrjb 7y agoPerl 6 is probably a great language, I'm not very interested in it, for the reasons someone might pick it, I'd probably pick a different language; of course not for any logical reasons, but still. Perl 5 on the other hand is still a great language for lots of reasons. I hope Perl 6 is renamed and Perl 5 will become Perl again and it will be reinvigorated and more people will consider it again. Don't get me wrong, I don't use Perl day to day because of the type of work I'm doing at $DAYJOB, but people like to dump on it for all the wrong reasons or outdated reasons, but I still believe in it, and I think a lot of people still do but there just isn't the mindshare and no matter what we think about our industry and how it works, that ultimately means new developers won't use it.
- _pmf_ 7y ago> Perl 6 is probably a great language, Does it also have the unparseability problem[0] of Perl 5? That's a deal breaker for a lot of tooling. [0] https://perlmonks.org/?node_id=663393 https://perlmonks.org/?node_id=663393
- viraptor 7y agoThis specific problem is not a deal breaker in practice. You solve the problem by adding to the readme of the tool "If the arity of a function cannot be established, we assume no arguments and print an warning. Add {foobar} before the function to assume arguments. Sorry for inconvenience." No language tooling is perfect. We shouldn't expect that from Perl tooling either.
- _pmf_ 7y ago> No language tooling is perfect. Java and C# tools are pretty close. But yeah, it's generally hard for dynamic languages.
- nightcracker 7y agoParsing C++ is also undecidable.
- Qcombinator 7y ago
- veidr 7y agowhorl EDIT: no, I'm serious and that's a cool (enough) and available name with the right amount of historical correlation EDIT 2: plus it already has an emoji icon on most platforms: https://emojipedia.org/fish-cake-with-swirl-design/ https://emojipedia.org/fish-cake-with-swirl-design/
- deleted 7y ago[deleted]
- lelf 7y ago> s/Perl/$other_language/g I’m somehow not sure Perl6 has anything to do with that. > because they're tired of waiting for Perl 6 But…for what exactly? It’s already stable enough for use.
- mojuba 7y agoI think an interesting question is, if the developers of Perl 6 knew from the beginning that they are essentially designing a new language with a new identity, would their new language be different and to what extent?
- de_watcher 7y agoDevelopers now want to grab old folks by using old name and new ones by using new name. Politically they can do that because there is a Perl 5 faction existing because of the big differences between 5 and 6.
- cestith 7y agoWhy are Modula, Modula 2, and Modula 3 so different? Or PHP 3 and PHP 7? Or K&R C, C89, C99, and C11? Or ISO Pascal, Turbo Pascal, Object Pascal, and Delphi? There are many, many languages that have been closely related but with wildly different names. There have also been plenty of languages which shared mostly the same name but are very different. It might be easy to see a mistake here in hindsight, but when the project first started that was much less clear.
- cutler 7y agoI don't get all this "Perl 6 is a different language" nonsense. It was created by Larry Wall and retains all the characteristics of Perl 5 whilst adding a lot of great stuff from other languages. Sadly, performance prevents it being taken seriously in production.
- jhanschoo 7y agoFWIW, C++ is a different language from C, and C code is more C++ compatible than Perl 5 is for Perl 6.
- markbnj 7y ago> FWIW, C++ is a different language from C It's been 20 years so my information could be very much out of date, but at that time anyway I would not have said this statement was true. C++ then was a superset of C, and any C++ compiler was capable of compiling ANSI C.
- sbmassey 7y agoEven back then, C++ introduced new keywords, so valid C code like int new; would not compile in C++.
- markbnj 7y agoThat's true, as a superset it reserved words that had not been reserved before... still think it's a stretch to call it a different language though.
- earenndil 7y agoYour information is very much out of date. C++ makes a few important changes that make most c code incompatible. #1, implicit cast between void and non-void pointers is not allowed, so something like: int *x = malloc(sizeof(int) * 15) is legal c, but in c++ you would have to cast the malloc call. Also, type of character literals is int in c but char in c++. String literals are const only in c++. Functions that take no arguments must be declared as taking void (as in void func(void)) in c, but simply () in c++.
- jefftk 7y agoThis makes a lot of sense. Renaming Perl 6 means: * Perl 5 can continue being "perl" and have a future. People with existing perl codebases won't think they're going to need to upgrade. * Camilia/Raku/etc can be considered on its own merits. The C/C++ analogy is a good one: when things are different enough you stop expecting everyone to "upgrade" and instead are making a different language.
- jschwartzi 7y agoSpeaking as someone with an existing Perl codebase in an embedded Linux system, we were planning on replacing it with Lua anyway because that would shave a solid 20 MB off the image size with no downside.
- derriz 7y agoI don't see any future for Perl5. Through a type of Osborne Effect - https://en.wikipedia.org/wiki/Osborne_effect https://en.wikipedia.org/wiki/Osborne_effect - the development of Perl 6 has also killed Perl 5. Few or none will reach for Perl5 these days for new development - Python or Node.js have obliterated Perl as contender in the space it used to dominate and I don't see Perl5 ever muscling it's way back. Fairly or unfairly, Perl5 is viewed as a legacy tool these days.
- jpm_sd 7y agoI suggest "Perl Nukem Forever"
- DonHopkins 7y agoPerhaps something onomatopoeic like "$#_@;\>&%}`[*~!^)"
- coldpie 7y agoAs a non-perl programmer, the mnemonic descriptions in the perlvar manpage crack me up. They probably are useful and make sense to perl programmers, but from the outside, they look like parody.
- DonHopkins 7y agoThe whole "Perl is easy to learn because it borrows from other languages" argument is based on a very specific set of historical assumptions about which "other languages" everybody knows, and what associations they have with each punctuation character from different shells and languages and utilities and operating systems and config files circa 1987, that is just totally obsolete these days.
- jandrese 7y agoBash still uses the same variable names. Are you saying nobody writes shell scripts anymore? Plus, you can always "use English;" if you want less cryptic names.
- DonHopkins 7y agoBash didn't exist when Perl was invented in 1987. Bash was first released two years later in 1989. In 1987 there was the Bourne shell sh, and there was csh and derivatives like tcsh, and there was the Korn shell ksh and its derivatives, and they each had their own unique quirky menageries of subtly nuanced punctuation and syntax and variable names. And of course there was sed, and awk, and C, and even BASIC.
- deleted 7y ago[deleted]
- dragonsh 7y agoI think the name Camelia or Raku is fine, no need to argue over it forever. During this renaissance period of computer languages in history, it will be nice to get this out and iterate. Given there are plethora of choices today like go, rust, Nim, elm, elixir, Scala, julia, crystal, F#, D etc. trying for developer mindshare which is a limited resource speed is of essence. Indeed with parrot VM besides perl 6 developers can be truly polyglot with same toolchain. So move forward, it's still a great addition. I feel parrot is truly open source, better than Graal no Oracle involvement.
- riffraff 7y agoparrot (as a multi language vm) has been dead for a long time, the GraalVM is probably the current best bet for a polyglot platform.
- dragonsh 7y agoYeah that's sad Perl 6 moved to moarvm[1]. I guess necessary evil to have performance which they can't get out of parrot. Hopefully someone pick up Moar with Rakudo and make it multi-lingual. Given Oracle involvement in GraalVM, it will always be a risk for open source development. [1] http://www.moarvm.org/ http://www.moarvm.org/
- pvaldes 7y agoMaybe Perl 5 should be renamed to Perl 7...
- AlexanderDhoore 7y agoYou say this as a joke, but that might actually be a good idea.
- DonHopkins 7y agoThen what's the next version of Perl 6 supposed to be, Perl 8? And the next version of Perl 7 will be Perl 9... From then on their version numbers will leapfrog each other to keep Even Perl and Odd Perl in parity.
- beefhash 7y ago> Then what's the next version of Perl 6 supposed to be raku 2? Perl 5 gets the Perl name back and gets a version number leap to show it's not dead yet and raku is off doing its own thing with its own version numbers, probably hitting 1.0 barely before GNU Hurd.
- DonHopkins 7y agoRakuier PINP: PINP Is Not Perl
- rectang 7y agoI agree. It would make a statement about future maintenance of the language, which is used by a vast amount of existing software.
- type0 7y agoSure, in the same vein as PHP 5 was remained to PHP 7
- grayed-down 7y agoThis is a great idea. If Perl 6 got a new name, some new branding, and Perl 5 added a few new features and polish, the language would suddenly awaken from its 20 year nightmare.
- peterwwillis 7y agoI wish Perl 5 was being renamed. As a language, it's annoying, but as a tool, it's possibly the best programmable tool ever made.
- AlexanderDhoore 7y agoSerious question: what does Perl 6 bring to the table? What advantage does it provide over Perl 5, Python 2/3 or Ruby? I could google this (which I will), but give me the HN summary. What do you think is a good reason to use Perl 6?
- patrickas 7y agoOff the top of my head: Concurrency and parallelism using high level and low level APIs. There is no GIL. Grammars which are like regular expressions on steroids for parsing. ( admittedly still not optimized for speed) Gradual typing, you can go from no types at all for short one liners, to using built in types, to defining your own complex types for big programs. subset Positive of Int where { $^number > 0; } #create a new type called Positive multi factorial(1) { 1 } #multi subroutines that dispatch on type multi factorial(Positive \n) { n * factorial(n-1) } #say factorial(0); #Error type mismatch #say factorial(5.5); #Error type mismatch say factorial(5); #120 hyper for (1 .. 1000) -> $n { #use hyper indicate for loop can be run in parallel on all available CPUs say "Factorial of $n is { factorial($n) }"; #Gives correct results by automatically upgrading to big int when needed }
- cestith 7y agoFour of my favorite things are the built-in MOP, the syntax for declaring values and their traits in objects, hyperoperators, and native support for user grammars rather than just regexes and parsing modules.
- daotoad 7y agoAdd to these multiple dispatch and support for literate programming. There's also a nice interface for writing command line utilities that takes advantage of the above. See my Christmas themed 2018 Perl6 Advent Calendar article on the topic: https://perl6advent.wordpress.com/2018/12/16/day-17-checking-your-list-twice/#more-7350 https://perl6advent.wordpress.com/2018/12/16/day-17-checking...
- thesuperbigfrog 7y agoPerl 6 should definitely be renamed so that Perl 5 can just be Perl. An easy way to see this is to simply look at the mascot for each language. Perl_5 => Humphrey the Camel (See https://www.perl.org/ https://www.perl.org/) (I am not sure if the camel actually has a name, so Humphrey seems like a good name for a camel mascot.) Perl_6 => Camelia the Butterfly (See https://perl6.org/ https://perl6.org/) They are very different and the languages are too, so why should the languages both be called "Perl X" ?
- Stubb 7y agoI haven't looked at Perl in years, having long ago switched to Python/SciPy, but now I see that Perl 6 doesn't have GIL, something that Python has been unable to shed. So now a language that nobody cares about anymore solves the #1 problem that I have with Python. We are truly blessed to have so many shitty implementations of dumb programming languages to choose from these days!
- Grinnz 7y agoI am a Perl user not Raku, and Perl had almost the opposite problem where its threads are concurrent but too badly designed to be useful. But from what I have seen, Raku is second to none in this capability.
- Stubb 7y agoBeing able to do a multi-threaded map() would be divine. In Python, you're creating/destroying a new process and using IPC to seed the state info and return the results for each element in the iterable arg. If the function in question runs quickly, it ends up being faster to do it single threaded.
- Grinnz 7y agoIt's not going to be efficiently threaded like in Raku, but this is also possible in Perl 5 with a few modules from CPAN. https://metacpan.org/pod/IO::Async::Function https://metacpan.org/pod/IO::Async::Function will maintain a preforked pool of processes (on Unix) or threads (on Windows), and return Futures, which can be used by fmap_concat from https://metacpan.org/pod/Future::Utils https://metacpan.org/pod/Future::Utils to make a very map-looking iteration. The experimental https://metacpan.org/pod/Future::AsyncAwait https://metacpan.org/pod/Future::AsyncAwait will make this even more natural in the future.
- Stubb 7y agoI'm continually astounded that threading involves jumping through so many hoops in 2019. If you want a language that provides a REPL and easy threading, your choices are few and far between.
- DangerousPie 7y agoAs an outsider who hasn't written perl code in more than a decade this all makes a lot of sense to me. I think of Perl 5 as something "outdated" because I know that there is a language called Perl 6. When I think of Perl 6 I am not particularly interested in it because I assume it's more or less the same as the "old" Perl, which I don't use and didn't really like back in the day. Renaming Perl 6 to something else would help with both of these problems. That said, I wonder how much damage has already been done at this point and whether renaming it now will still be very useful. There are a lot of references to Perl 6 out there already, so convincing people that Perl 5 is the latest version of Perl again will be tough.
- mkozlows 7y agoThere's no saving Perl 5; it's a legacy language in legacy maintenance mode for good reason. Renaming Raku/Camelia could help that language quit being saddled with the perception that it's also legacy in the same way, though.
- roryrjb 7y agoWhat good reason is that?
- mannykannot 7y agoI still use Perl 5 for some tasks, but my rule-of-thumb is that if I anticipate wanting to use references, I will go elsewhere.
- jerf 7y agoI suggest and use the opposite rule of thumb, "always use references". It tends to simplify things. Python writes the same rule into the language itself.
- mannykannot 7y agoWhen I used it for larger tasks, I did the same. Nowadays, the consequence of my rule is that Perl 5 sits in my toolbox between Awk and Python.
- meijer 7y agoAs a German, I don't like the name "Camelia" very much because it is associated with hygiene products here (brand name). "Raku" sounds nicer for me.
- cestith 7y agoAnecdotally, "Meijer" is one of my favorite retail chains in the US.
- Grue3 7y agoRaku is a good name (can be abbreviated to 楽 as a bonus). Camelia is too long and is already the name of the mascot. Ofun is terrible (nothing like a product implying it's "fun" by literally including "fun" in the name).
- tomlong 7y agoEspecially when it can readily be pronounced "Zero Fun"
- gwd 7y agoThe author (and many comments here) make good cases for renaming; but other than, "Perl 5 is dead, long live Perl 6", what case is there to be made for keeping "Perl 6"? Having written some terrible scripts in perl 20 years ago (and still occasionally using it as an awk++), I am interested somewhat to learn what Perl 6 is like. But honestly, Rust and Swift are both ahead of Perl 6 in the "interesting new languages to learn when I have some free time" queue (having picked up Go over the last few years). (edit: spelling)
- mkozlows 7y agoTo my mind, the blockers for Perl 6 adoption in order of importance have been: 1. The name, saddling it with the legacy of Perl. (I say this as someone who really liked working with Perl back in the waning years of the old millennium, and believes that Perl was visionary in pointing the way to the state of modern programming... but also that it had some limitations that have only become more glaring over the years.) 2. The coyness around whether it's "done" or not. Right now today, as someone who has paid attention to Perl 6 and even written some toy code with it, I do not understand its release status at all. That's absurd. 3. The insistence on branding sub-components of it and exposing that branding. Yes, it has a VM. Yes, it has a compiler. But why do people talk about ParrotVM and Rakudo as if they're different things? Java has a compiler and a VM, they're called "javac" and "jvm." This wifty "no, Perl 6 is the standard, the software you're running is Rakudo and Parrot" distinction is totally irrelevant to anyone actually wanting to write code, and weirdly confusing. 4. In a distant, distant last place: any actual functional stuff about the language.
- CogitoCogito 7y ago> but also that it had some limitations that have only become more glaring over the years. I don't have any real experience with Perl, so could you maybe expand a little? I'm curious about what you think the limitations are.
- mkozlows 7y agoI mentioned it in another comment, but a really obvious one is that functions in Perl don't have parameters. Every function just takes in a list, and can do whatever it wants with that list. This page gives a good overview of the situation: https://perl101.org/subroutines.html https://perl101.org/subroutines.html There's a kind of elegant flexibility to that, but it also makes it really hard to program reliably in the large, to build useful tooling, or even to glance at a function and know what you should pass it. Beyond that, classic Perl was full of things that make it quick to write small programs (as CGI scripts were at the time) without a lot of boilerplate, but which don't scale up. (Perl 6 is very different, and has an almost comically flexible/powerful function signature system (https://docs.perl6.org/type/Signature https://docs.perl6.org/type/Signature). Whether or not you like Perl 6's stuff, it's nothing at all like Perl 5's.)
- mmaunder 7y agoI'm sorry but Perl 6 isnt relevant IMO. It took too long. I was a Perl developer at etoys.com in 2000 and BBC in 2001. I wrote OneMusic for Radio1 and even convinced the BBCs uptight ops team to run it with modperl so it could handle the high traffic it did. I also created the job search engine WorkZoo in modperl, one of Time Magazines top 50 sites of 2005 and Indeed's main competitor at the time. Perl6 was promised. Then it never happened. It's now an almost quarter century later. The world has moved on. Taking that long for a single version update in a language is not reasonable. I loved Perl. I still love Perl5. But I've moved on and have 100% blocked Perl6 from my psyche and list of expectations. No one I know uses it. I am not excited by it. I dont need it. And I don't care to hear these discussions about minutia related to it. It's a debacle and a case study in the failure of what was a beautifully ugly practical performant language.
- mkozlows 7y ago... which is the whole point of renaming it, right? "Oh, it took too long to update Perl and now Perl is dead" is true. "Raku is an interesting new language with some neat features, and excels at this particular type of problem" can also be true. But nobody can hear this message while they keep thinking about Perl.
- 0xffff2 7y agoI doubt it. "Raku is an interesting new language with some neat features..." will be met with "Oh, you mean Perl 6? lol." If Perl is dead, renaming the last version isn't going to change anything.
- meowface 7y agoMost likely, but as a Hail Mary last-ditch effort, it seems reasonable and probably better than nothing. "Raku" sounds at least 1% more interesting for a dev to look into trying than "Perl 6".
- joosters 7y agoPerl isn't dead. It's a perfectly good, stable language with excellent library support. It's just not sexy and new, so there's no buzz about it. Perl6, on the other hand, is effectively another language altogether, and I hope they rename it completely to stop the confusion.
- dkarl 7y agoRoutinely I see in numerous online discussions that people refuse to even consider Perl 6 because they hate Perl. Or there are younger people who think of Perl as "their grandfather's language" (in much the same way people in my generation view COBOL). I am not a fan of Perl, but this feels tragic to me. Perl was so radically different. I remember being on Perlmonks way back in the day, and someone would post a question about why their code didn't work, and there would be dozens of people who could instantly, intuitively post a corrected version of the code, but then the poster would say "oh, shit, what was my code doing? and why does the correct code do something different?" and you'd be lucky if there was a single person (cough chromatic) who could explain it. And none of the Perl fans cared, because Perl made them extremely powerful and productive, and they could (almost always) confidently produce a line of Perl code that did what they wanted. The analogy to natural language carried further into practice than Larry Wall could have dreamed. Nobody worries that the difficulty of resolving linguistic conundrums impairs their ability to have a conversation, and the Perl ninjas in my company enjoyed a very close and chatty relationship with the systems they worked on. I'm the opposite kind of person, who got sick to his stomach looking at a line of code like !#$foo->%_[] (note: not real Perl) not knowing why it worked, even if I wrote it and knew that it would work. Even now, I have a nagging fear that if I executed "!#$foo->%_[] (note: not real Perl)" it would print "Yes it is! Ha ha. Love, Larry" to the console. I can't stand that, so Perl was never for me, but I still hope that against all odds this long, drawn-out apparent deathbed scene turns out to be the middle of a successful convalescence.
- Grinnz 7y agoAs a Perl aficionado, thank you for this, it is rare that anyone who does not enjoy Perl will express a positive opinion for it.
- anthonybsd 7y agoI do not enjoy Perl, but I have a positive opinion of it :) I launched my career in the late 90s as a Perl/XS/CGI (later mod_perl) developer and have many fond memories of it. I also have seen enough cases of Perl codebase deterioration to acquire significant distaste for it as far as enterprise projects are concerned. I enjoy using it for one-liners and small scripts here and there because it's VI-like in terms of being ubiquitous. I just don't programming Perl in teams larger than 1. Makes sense?
- foobar_ 7y agoRaku, Camelia and Rakudo are stupid names. Perl++ is a good name. C and C++ are different enough and live alongside each other.
- cat199 7y agobut this brings up C++, if in name only, which wouldn't always win you fans..
- cestith 7y agoPerl# ?
- foobar_ 7y agoThe cool part about old 90s Perl5 was ... it was doing its own thing. The best part about everyone hating you ... gives you the freedom to do precisely that. I don't like the proposed names because they seem to imply a new language. You need Perl in the goddamn name. I honestly think the biggest mistake that Perl5 made was going the OOP garbage way, which complicated the language as it was implemented as a hack. And everyone just said ... look Perl, ha ha ... can't do OOP! OOP in all its forms is a mistake. Small talk OOP, CLOS, Java OOP .... sheesh it's just a hash with sub refs. C gives you function pointers and structs. OOP should have been limited to just fucking that. Encapsulation is a mistake. Inheritance is a mistake. Polymorphism is useless in a dynamic language.
- wombatpm 7y agoI learned Perl4 in grad school and it was a life changing tool to automate my analysis workflow. With it I was able to script complex solutions that drove stepper drivers and CCD cameras on a microscope for data and image collection. I stayed through the Perl5 change over and thought it was good. Then I tried OO programming. And cried. And read that Perl 6 would make it better. But I needed something now, on a windows box, and free. That was 2003. I tried Python and loved it. Higher Order Perl made me appreciate what Perl could do, but the state of Perl 6 and lack of progress kept me away, as the features I most wanted were always fixes coming real soon now. I STILL program python. Perl had me and lost me. Perl might not be dead, but it is dead to me.
- aduitsis 7y agoWhat I got from mingling with the Perl community: The single most repeated advice (indeed Larry Wall himself has said it repeatedly), is that one should use whatever tool will allow one to carry out the task at hand and generally get things done. In that sense, Perl never had you because Perl probably isn't interested in "having" anyone. Maybe helping out people carry out their work, but not having them. It is about getting things done, without trying to be the next big thing in CS. At least that's what I'd like to believe. If Python helps you carry out your work better, you should most assuredly and definitely use Python. Ditto with PHP, Go, and all the rest. And Perl.
- pvaldes 7y ago> With it I was able to script complex solutions that drove stepper drivers and CCD cameras on a microscope for data and image collection. Can fall to mention that this sounds extremely sexy...
- daotoad 7y agoIf you like OOP you should check out Moose and Moo in Perl 5. https://metacpan.org/pod/Moo https://metacpan.org/pod/Moo If you want regular Perl5 for Windows, Strawberry Perl is quite nice. http://strawberryperl.com/ http://strawberryperl.com/ Perl6, OTOH, has powerful OOP features like traits all built on a powerful, standard meta object protocol. Its functional programming features have evolved beyond Perl5's excellent support. Come back and try these things out.
- cannedslime 7y agoI rarely see Perl in the wild today. Only companies that are too big too fail and too cheap to move on still clings on to Perl, the big "index" sites of the late 90'ies that somehow haven't been completely run into the ground by silicon valley giants like monster, facebook, linkedin etc.
- mcdermott 7y agoPerl 6 was a huge mistake; it's a different language and should have never had the same name. I support renaming it so we can all forget about it and have Perl 7 be a direct, mostly backwards compatible descendant of Perl 5 with feature enhancements. This whole Perl 6 nonsense was the reason I jumped to Python many years ago.
- cestith 7y agoI don't think the language was a mistake, but it looks like the naming was.
- mikl 7y agoUntil Perl6 is actually released, it doesn’t really matter what they call it. (yes, I know they have functional snapshot builds, but as long as there’s not a final "6.0" (or "1.0") release, expect most devs to steer clear of it. Few people (masochists, mostly) want to use an ‘experimental’ programming language for important work).
- dragonwriter 7y ago> Until Perl6 is actually released, it doesn’t really matter what they call it. > (yes, I know they have functional snapshot builds, but as long as there’s not a final "6.0" (or "1.0") release, expect most devs to steer clear of it. Few people (masochists, mostly) want to use an ‘experimental’ programming language for important work). The “1.0” for the Perl 6 spec (6.c, because reasons) was released in 2015; the stable implementation in Rakudo was a little later but years ago. Current Rakudo has a stable, production-ready implementation of last year's 6.d version of the language spec. So we’re well past the threshold you suggest.
- Qcombinator 7y agoThen it should have been called "1.0". Calling it "DEFINITELY NOT 1.0" while deciding that that is secret P6 code for "really means 1.0" is awfully bad marketing. (More seriously, slow performance, missing features, bugs, etc. were part of the reason for not calling it "1.0", but I would agree that to be really successful, the language needs a release that is called 1.0 and acts like it.)
- dragonwriter 7y ago> Then it should have been called "1.0". 6.c was described, both before and after its release, as being the “1.0” release of the Perl 6 language. > More seriously, slow performance, missing features, bugs, etc. were part of the reason for not calling it "1.0" No, they weren't. The first “production-ready” release of Rakudo Star release was shortly after the 6.c spec release, in version 2016.01 (Rakudo Star uses date-based versions numbers.) If they were using semver-ish numbering for Star releases rather than dates, this would have been the 1.0 implementation (as opposed to spec) release.
- hyperpape 7y agoI think this is a good idea, but there's a decent chance that some people will mishear the change as "Perl 6 is cancelled, Perl is dead". To be honest, I'm not sure anything can change the decline of Perl. There will continue to be Perl projects and Perl shops for a long time, just as there are COBOL projects, and COBOL shops. There will even be some new projects. But many projects will die, some companies will go out of business or migrate, and the ecosystem will continue to ossify.
- k__ 7y agoWhat did Perl do better than others when it came out?
- goto11 7y agoA super powerful and flexible alternative to shell scripts. It was widely used for systems administration tasks.
- yarrel 7y agoWhat others?
- k__ 7y agoProgramming languages.
- marcosdumay 7y agoIt was shell scripting with reasonable arithmetic and an incredibly good support for text consumption and regular expressions. Everything you'd miss on a normal shell. But it scales only slightly better than sh into large programs.
- k__ 7y agoI see. Would you consider Bash on-par with Perl?
- marcosdumay 7y agoNo, I wouldn't. Perl 5 is much more powerful. But I wouldn't choose either for a moderately large script.
- k__ 7y agoAh okay. But back in the days? Bash seems to be released a year or so after Perl.
- zests 7y agoI want to write some scripts that are _slightly_ too complicated for bash. Basically just implementing some simple scripts that have a couple options/args and I want to use another tool. How good would perl 5/6 be for this? If not perl, anything similar that's not python? I want to learn something new.
- Grinnz 7y ago"This would be annoying to write in bash" is a very popular use case for Perl (5).
- ttkciar 7y agoYes, what Grinnz says. "Bash on steroids" is one of perl's strongest use-cases. It's why a lot of system administrators learned perl.
- Qcombinator 7y agoSounds like the perfect opportunity to check out P6. It's stable enough and has a lot of cool features if you want to learn something new. It even has built-in multi-dispatch command-line arg-processing: https://docs.perl6.org/language/create-cli https://docs.perl6.org/language/create-cli
- perlperson 7y agoThis is a _perfect_ case -- to get started, you can just put `shell` in front of every line #!/bin/bash echo hello change to #!/usr/bin/env perl6 shell "echo hello" then for arguments, try making `foo.p6` #!/usr/bin/env perl6 unit sub MAIN($name,:$times,:$language); say $name, $time, $language and run ./foo.p6 --help
- daotoad 7y agoAs I said elsewhere in this thread, check out my article for the 2018 Perl6 Advent Calendar. https://perl6advent.wordpress.com/2018/12/16/day-17-checking-your-list-twice/ https://perl6advent.wordpress.com/2018/12/16/day-17-checking... I walk through the development of a utility for auditing Santa's Naughty and Nice lists. Along the way, I introduce literate programming, multiple dispatch, types, type subsets, links to documentation, perl6 collections, and File IO. And, I've been told I managed to do all this without making the reader they've been dragged over rough ground behind a certain festive sleigh. The key thing to remember when you start learning a Larry Wall Language is that you only need to worry about the parts you need to worry about. It's more like learning a natural language than a programming language. Learn how to say the things that are important to you, and it will serve you well even if you speak with an accent.
- nvr219 7y agoI love open source drama
- deleted 7y ago[deleted]
- dmix 7y agoI've got to agree Raku is way better than Cameila. Although I understand why the female developer couple would want a female name. It just doesn't sound like a programming language and shorter the better (nothing beats Ruby).
- cestith 7y agoCamelia is the name of the butterfly mascot, hence the suggestion to use it as the name of the language. rakudo, the language tool, basically translates as "way of the camel" playing on the use of the camel as Perl's O'Reilly book mascot. "Raku" or "raku", would basically be calling the language "camel" and the tool "way of the camel" which has a certain appeal as well. However, the camel has never been really directly associated specifically with the new language except in the names rakudo and raku. So as I see it, there are good arguments for either side of this. Knowing Liz and Wendy I doubt their suggestion has much more to do with being girly than my feelings on the matter. I think it has more to do with making the clean break really, really clean. Unfortunately all this furor within the community and even from without has nearly convinced both ladies to leave the community they've been pillars of for two and a half decades. They've suffered personal attacks over this and their participation in anything Perl related is likely to be curtailed if not ended. It's a sad, sad day because Wendy's one of my favorite people at the conferences.
- dmix 7y agoOh apologies I made an assumption there I probably shouldn’t have. To me naming is was mostly how it rolls off the tounge so I’m not a fan of multi syllable words that aren’t super common. I’m also not a fan of ‘clever’ words that have dual meaning, like tattoos it should mostly be an aesthetic thing. But I’m not surprised when I hear communities responding to change poorly. Any large community has this problem and it’s best to ignore the rancour. Not everyone should have an opinion and there’s nothing that attracts more than a name. So it will come down to personal taste. I’d 100% defer to the primary devs on this one.
- mrtweetyhack 7y agoYes it is. Earl.
- gmiller123456 7y agoI think it was CPAN that killed Perl, at least that was a major nail in the coffin for me. I have no idea what the CPAN of today is like, but back in the mid-late 90's it was horribly unreliable. There were dozens, if not hundreds of modules that did the same thing, and a lot of them had major bugs. But installing one was the big issue, as it would always choose the latest release of any module in the dependency chain, including the perl interpreter itself. And this was done without any hint as to whether the module actually worked with the latest versions of those modules. So, you'd end up upgrading a bunch of modules, very likely breaking things that worked. And at the end, it'd "upgrade" the perl interpreter. And by "upgrade" I mean install a new copy, replace all OS references to the new version, but not include any of those modules you just installed. So you had to re-install everything again. Perl's main use at the time was developing CGI scripts. It had big disadvantages over things like PHP and Netscape Commerce at the time, but people still seemed to like Perl. As complex web side code grew more complex, requiring a lot of 3rd party components to get Perl to do anything, people seemed to abandoned it pretty quickly. I still use Perl today, version 5. Mostly just to process text files, but I still don't use any 3rd party libs.
- cestith 7y agoThere are many tools for installing modules. Almost all of them default to the latest available package but can be told a version. I suggest looking into local::lib and then either a combination of cpanm and a Cpanfile or using perlbrew.
- ether_at_cpan 7y ago> But installing one was the big issue, as it would always choose the latest release of any module in the dependency chain, including the perl interpreter itself. You are mistaken. No cpan client is capable of upgrading perl itself. If a cpan module declares a dependency on a perl version later than what you are currently running, the installation simply fails (as what would happen if there is a dependency declaration on a module that is shipped with core and is not upgradable separately, e.g. 'strict' or 'POSIX').
- 7y ago
- nneonneo 7y ago> Perl 6 performance has now gotten to the point where it's often comparable to Perl 5 or surpasses it. It still needs some work in this area, but the work is clear, the goals are straightforward, and Perl 6 is going to easily oustrip Perl 5 in terms of performance. If the Perl 6 community wants to rename, it's perhaps the perfect time to do so. It doesn't look like a bad choice if performance is a primary concern. Perl6 has been under development for over a decade at this point, and this equivocating statement is the best that can be said about performance? If the "work is clear, the goals are straightforward" and Perl 6 should easily outstrip Perl 5 on performance, then by gosh they should demonstrate that. Plenty of comments are mentioning slow performance. Not having used Perl 6 myself, I can't comment on it, but the fact that this seems to crop up a lot is really worrying. I've heard varying things - regex/grammar are slower than Perl5, startup time is really slow, etc. And yes - I realize that technically the most popular compiler/VM combination Rakudo+MoarVM hasn't had that full decade of development, and that the spec is "in theory" performant. None of that matters to developers who just want to use the language... If performance is a major blocker to adoption and it's as straightforward to fix as suggested - it should get done. Otherwise, the empty promises will continue to hurt adoption.
- bjoli 7y ago"As fast as Perl 5" means "faster than python and ruby". Every time someone complains about python performance they are usually told that it doesn't matter. If performance was really that important, people that wanted dynamic languages would all be using luajit, SBCL, chez scheme (or any of the other 10 schemes that run laps around python/ruby) and lately also JavaScript.
- Ultimatt 7y agoYou might enjoy this talk "Perl 6 performance update" from last week. Assuming you're actually that interested https://www.youtube.com/watch?v=QNeu0wK92NE https://www.youtube.com/watch?v=QNeu0wK92NE
- proverbialbunny 7y agoPerl 5 is quite a speedy language. Getting Perl 6 up to Perl 5 speed is impressive. Part of the reason the language looks scary from a distance is it's $sigils, which speed up the interpreter.
- amptorn 7y agoThey renamed Perl 6 to "Raku" last year!! Am I losing my mind? This is a done deal! https://marketing.perl6.org/id/1541379592/pdf_digital https://marketing.perl6.org/id/1541379592/pdf_digital
- Grinnz 7y agoThat announced that it could be used as a second name, but provided no further guidance, so Perl 6 is still used by many thus its problems are still just as present. This proposal would be to actually consistently use Raku as the name of the language.
- amptorn 7y agoWouldn't it have made more sense to hold off on the first announcement until there was consensus on a single new name, instead of having two or three inconsistent namesoperating simultaneously for a year? Neither of which might be the final one?
- Grinnz 7y agoA lot of things would have made more sense in hindsight, but it's not where the community was at the time, and ultimately Larry said no to a straight rename. He is taking less of a role now so it can be revisited.
- xweb 7y agoI haven't worked with Perl in 20 years, but obviously totes: Perl++ amirite? joking
- cryptozeus 7y ago“Perl 6 is a sister language, part of the Perl family, not intended as a replacement for Perl 5, but as its own thing - libraries exist to allow you to call Perl 5 code from Perl 6 programs and vice versa.” Umm.
- daotoad 7y agoYou can also call Python from both languages. It doesn't mean they are the same. https://metacpan.org/pod/distribution/Inline-Python/Python.pod https://metacpan.org/pod/distribution/Inline-Python/Python.p... https://github.com/niner/Inline-Python https://github.com/niner/Inline-Python
- pavon 7y agoI think this is a great idea that is two decades too late. Many people say that python killed perl, and that is true for those who disliked perl. However, I think perl 6 killed perl for those who liked it, or could have liked it if they learned it. The knowledge that there was a new version on the way that would have all power of perl, but fixed many of its problems took the wind out of perl's sail, especially once it became clear how different it was going to be. Why invest time into learning perl 5, when perl 6 was just around the corner? How do I defend my use of perl 5 in production, when its own creators have moved on? Best to just concede the battle, and regroup for the war when perl 6 is ready ... and then it never was. I really think that both languages would be stronger today if Larry Wall et. al. had "marketed" perl 6 as a research sandbox for new ideas for language design, and then depending on where those ideas led them, pronounced it as either a successor to perl, or a new language when it was closer to ready.
- mark_l_watson 7y agoJeremy Howard (co-founder of Fastmail (Perl used for everything), co-founder of fast.ai, etc.) in his Lex Firdman interview this week, made some interesting comments on Perl and Larry Wall no longer taking enough interest in the language. I don't use Perl, but the comments were interesting anyway.
- sundarurfriend 7y agoLink: https://lexfridman.com/jeremy-howard/ https://lexfridman.com/jeremy-howard/ to the podcast episode that I guess you're referring to. Thanks for mentioning it, will check it out.
- vincent-toups 7y agoIf I ever wanted to program in Perl, I'd program in J.
- markstos 7y agoRebrand.
- ThomWilhelm3 7y agoThis is a bit like people arguing over the what noise should be made when the "tree falls in the woods and no one hears it".
- kazinator 7y agoAlthough the "Perl" name in "Perl 6" is basically wrong and misleading, it's also the only reason Perl 6 is a blip on anyone's radar.
- harry8 7y agoperl5 needed a single switch to make it loosey-goosey anything goes otherwise have use strict and -w by default. That one decision cost the language so very much. I miss Perl. Python is what was pushed on me by employers and it's fine, it's perfectly acceptable. As is ruby and many others but I just miss Perl. I hope the Perl6/Raku folks get things happening in their tech and perception of it the way they might like. I think they deserve a break.
- mkorfmann 7y agoDid you see the Grammars in PERL?
- cyrc 7y agoSuggestion for rename: Pearl 1