Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Perl Programming

Larry Wall Approves Re-Naming Perl 6 To Raku (github.com) 100

Long-time Slashdot reader hondo77 notes that Larry Wall has given his approval to the re-naming of Perl 6.

In the "Path to Raku" pull request, Larry Wall indicated his approval, leaving this comment: I am in favor of this change, because it reflects an ancient wisdom:

"No one sews a patch of unshrunk cloth on an old garment, for the patch will pull away from the garment, making the tear worse. Neither do people pour new wine into old wineskins. If they do, the skins will burst; the wine will run out and the wineskins will be ruined. No, they pour new wine into new wineskins, and both are preserved."

"Perl 6 will become Raku, assuming the four people who haven't yet approved the pull request give their okay," reports the Register, adding that Perl 5 will then become simply Perl.

Dozens of comments on that pull request have now already been marked as "outdated," and while a few contributors have made a point of abstaining from the approval process, reviewer Alex Daniel notes that "this pull request will be merged on October 14th if nobody in the list rejects it or requests more changes."
This discussion has been archived. No new comments can be posted.

Larry Wall Approves Re-Naming Perl 6 To Raku

Comments Filter:
  • Finnish "raakku" (Score:4, Interesting)

    by TeknoHog ( 164938 ) on Saturday October 12, 2019 @05:41PM (#59300834) Homepage Journal
    means freshwater pearl mussel. Just sayin'.
  • by theshowmecanuck ( 703852 ) on Saturday October 12, 2019 @05:51PM (#59300864) Journal
    For those of us not into Perl politics. Seems unnecessary. For someone just coming on this, it looks like it could be another case of people thinking that if they change what you call something, it will fix any past evil. So what's the shorty story? No I don't want to look it up myself. This is a forum posting technical news, I think it is reasonable to ask for a synopsis.
    • Because it's a completely different language.
    • Re:Why? (Score:5, Informative)

      by vadim_t ( 324782 ) on Saturday October 12, 2019 @06:23PM (#59301006) Homepage

      The idea that "Perl 6" in hindsight was a mistake. Initially the idea was a VM that would run Perl 5 really fast. And that there would be a beta in a year or two. And then Larry Wall started coming up with a huge list of changes.

      That sent a message to people: Perl 6 will be out soon, and there will be significant changes, probably backwards incompatible. Best not to do anything too important on Perl 5 right now, and wait until 6.

      And then Perl 6 failed to happen. But there was the perception that Perl 5 would die sooner or later, so work started shifting away from it. But there wasn't a functional Perl 6 either. And another problem emerged: Perl 6 isn't compatible with XS, so even if the syntax was compatible, a huge amount of modules wouldn't work and would need a complete rewrite. So Perl 6 wasn't really an upgrade to Perl 5, but a new, different and incompatible language.

      The idea behind the name change is to recognize that the initial plan failed and to acknowledge the difference. People should treat Perl 6/Raku as a new, different thing that might have some similarities in style to Perl 5, but not expect any sort of continuity or upgrade path.

      • Re:Why? (Score:4, Interesting)

        by Aighearach ( 97333 ) on Sunday October 13, 2019 @01:37PM (#59303342)

        The idea that "Perl 6" in hindsight was a mistake. Initially the idea was a VM that would run Perl 5 really fast. And that there would be a beta in a year or two. And then Larry Wall started coming up with a huge list of changes.

        A needless slander. I was there, it wasn't like that at all.

        As Larry Wall said back then; Perl 5 was his rewrite of Perl 4. Perl 6 was the community's rewrite of Perl 5. It was the community that wanted all these new things. Perl 6 failed to happen for a long time, but by the time I jumped ship in 2004 it was already usable. The problem wasn't that it didn't work, or that modules didn't work, the problem was that it was a Homer Car of a language. It was fear of the new code that some people were writing. Perl was already a difficult language to read, the idea of all these new features was just ridiculous to the majority of people who had no use for them.

        There was enough backwards compatibility that old code wasn't really the problem. For the most part, people didn't even try.

        • by doom ( 14564 )

          It's hard to get stories like this completely accurate, but it pretty much is the case that Perl 6 started out as the next perl, but once the decision was made to break backwards compatibility and do a total re-design, the project diverged into developing a totally new language (however "perl flavored" it might seem), and things dragged on forever...

          From the point of view of a perl5 person, the question "why should we switch?" never really had a good answer, because there was and is nothing really all th

        • by vadim_t ( 324782 )

          Which community you mean? The community of wizards that hack on the interpreter's code? Maybe.

          But there's a larger community of people who write Perl and don't delve into the arcane internals, and I would say a good amount of those were disappointed.

          The compatibility isn't there for anything non-trivial. You can't port a Wx app to Perl 6 because there are no Perl 6 bindings. The Perl 5 can't work because XS isn't a thing in Perl 6, and all this means that a huge amount of things on CPAN can't be ported to P

          • It was an open process where the community would submit RFCs and discuss them, then Larry Wall would grade them on the quality of both the problem, and the solution.

            There community was merely all the people who were interested in being involved in the process back in 2001 or whenever until whenever they froze the process.

            I'd never hacked on the interpreter code, and I participated.

          • If Wx isn't that large, I might take a stab at porting it... who knows. :)

    • If they'd have named it Raku 20 years ago, I might still be a Perl hacker! LOL

      The short story is that Perl 6 is the language that never was, and remained so even after it was completed.

  • by gweihir ( 88907 ) on Saturday October 12, 2019 @05:51PM (#59300868)

    That will make it easier to ignore the gold-plated messed-up "second system effect" Perl 6 and get good use of simply "Perl".

    It is a bit tragic, because a lot of capable people invested a lot if time into Perl 6. It is still a failed project.

    • Re:Excellent (Score:4, Insightful)

      by oddtodd ( 125924 ) <oddtodd67 AT gmail DOT com> on Saturday October 12, 2019 @06:06PM (#59300944)

      >> It is a bit tragic, because a lot of capable people invested a lot if time into Perl 6. It is still a failed project.

      It could be considered a failed project, I suppose, but so was Multics, and the ideas and lessons learned from that helped to spawn Unix.
      The road to success is paved with many failures... where did I hear that?

      • by gweihir ( 88907 )

        You are certainly correct. What makes me a bit sad is that we still have not figured out how to do this right on the first attempt. But the effort is not all wasted.

      • I was quite surprised to learn that Multics did not fail. It was shipped and ran on dozens of systems for 20 years. Ada and Visicalc were built on it. Not as successful as Unix obviously.
      • by murdocj ( 543661 )

        The lesson learned from Perl is "don't do this".

        Perl is a horrific disaster, a hodge-podge of random stuff. I last used it close to 20 years ago and it still annoys me.

    • But does that mean I am now using Regex Raku-Style Pattern Extensions or Perl-Style Pattern Extensions?
      • by gweihir ( 88907 )

        Stay away form regexp pattern extensions if you want to keep your sanity! On a more serious note, I found that I never needed them. I had to, on occasion, implement some matcher myself though.

        • by doom ( 14564 )

          I had to, on occasion, implement some matcher myself though.

          And nothing can go wrong with that approach, eh? But the important thing is to be able to say you don't use those damn regexps.

          • by gweihir ( 88907 )

            Where did I say I was not using regexps? Oh, wait, I did not. I very specifically was talking about "pattern extensions" only.

      • Comment removed based on user account deletion
    • by doom ( 14564 )

      It is still a failed project.

      If you're expecting Perl 6-- I mean, Raku-- to be a drop-in replacement for some other language, then I suppose you might call it a "failure", but what it is is something entirely new. It is possible that it might turn out to be criticially important in some new field that we're not thinking about yet-- much as the original perl turned out to be key for Web 1.0 and the human genome project-- or perhaps not. At present a lot of us think it's fun to play with, which is more

      • FOCAL is fun to play with, You just need to spin up your PDP-8 emulator, or a real PDP-8/e if you have one lying around....

  • Thematic, then (Score:1, Offtopic)

    by Empiric ( 675968 )
    Jesus said, "I shall choose you, one out of a thousand, and two out of ten thousand, and they shall stand as a single one."

    --Thomas 23

    That's a lot of camels. Or more bipedal resources.
  • by Midnight Thunder ( 17205 ) on Saturday October 12, 2019 @06:33PM (#59301032) Homepage Journal

    The cynic in me asks if it even matters?

    In my previous job anything Perl was being migrated to Python and in another job the grey beard was so fed up of being the sole developer he is open to someone rewriting the tools in another language.

    As someone who hasn't followed Perl in depth for a while, is the development cycle still slow? Everything felt like a committee effort last I was there.

    • Perl niche was back in the mid-1990s because it had fast and efficient Regex processing. This was useful back then because Database systems were expensive and took up a lot of Computing power. Having a web site or a lot of other applications powered by Perl was quite useful, as it would rather easily do the job of a database, often working with flat files.
      The decline of Perl is the rise of the database. MySQL and PostgreSQL became competitive to other expense Commerical DB out there and also at that time

      • Re:Does it matter? (Score:5, Interesting)

        by Etcetera ( 14711 ) on Saturday October 12, 2019 @08:13PM (#59301284) Homepage

        Perl niche was back in the mid-1990s because it had fast and efficient Regex processing. This was useful back then because Database systems were expensive and took up a lot of Computing power. Having a web site or a lot of other applications powered by Perl was quite useful, as it would rather easily do the job of a database, often working with flat files. ...
        Other Languages like PHP, Python, .NET ... that were coming out took better usage of DB calls and really had their advantages in different areas. Thus making Perl obsolete.

        Perl did what it needed to do, the problem is technology changed in a way that undercut Perls primary benefit, text processing.

        I don't know that I would quite agree with that. Text processing (which includes rich text and data structure processing) is still very much a needed thing. What perl can't provide is *memory-constricted* data structure analysis in a useful manner, but that's only a certain subset of problems. Anything relational is already being handed off to your DB engine and while DBI may seem clunky, it still does the job it needs to. And there are plenty of us who still need the regex speed for memory or data streams that perl excels at.

        Where perl has truly missed out, IMO, is the rise of microservice scripting. I can't begin to tell you the number of tiny, poorly-coded python web services I've run into, most of which have a weird, complex array of specific dependencies necessitating a virtualenv that's annoying to move around. NodeJS is barely any better as a language framework, and is even more fragile as an ecosystem. Containers solve some of those problems, but that just offloads the complexity elsewhere. Perl really needed an easy onramp for creation of these microservices and there was such an aversion to it at that critical time that it missed the boat. (Ironic, considering its '90s era roots as *the* CGI language of choice, and half the web services out there are just python modules wrapped around an HTTPd listener, which describes the A and P in a LAMP Stack just fine.)

        Had perl been popular enough to displace the python bottle's of the world, it would have been strong enough to provide a counterpoint to the rise of server-side JS, which perl beats for performance and features in almost every respect.

        • by doom ( 14564 )

          And there are plenty of us who still need the regex speed for memory or data streams that perl excels at.

          Yes. Perl5 (which I can now, thankfully go back to just calling "Perl"), has full unicode support combined with one of the fullest-featured regular expression engines (the other guys are always playing catch-up, still). It's been one of the fastest scripting languages for some time--

          If the difference went the other way, there would be no end of smart guys trumpeting how much better their language

          • has full unicode support combined with one of the fullest-featured regular expression engines (the other guys are always playing catch-up, still)

            Full-featured in what way? Levels of unreadability and lack of code modularity in its first-order regex language? Surely not levels of performance. [swtch.com]

            • The NFA article shows a pathological example. In real life, for most regexes you are likely to encounter, perl's regex engine is exceedingly fast. One of the problems with using a DFA is that it tells you whether it matched but not why it matched. If the regex includes captures, you're out of luck. Also, for 25 years now perl's regexes have supported multi-line regexes with arbitrary whitespace and code comments, so it's very easy to write fully documented patterns
          • Slight off topic, but talking of full unicode support, I wonder whether Slashdot will ever take advantage of that in its current Perl based implementation. Well that and IPv6.

            Actually is the /. still open source?

        • It is not the language, it is the programmer.
          Well, it is the langusge, a programmer writing mediocre code in Python would write horrible code in Perl.
          I don't use Perl anymore since roughly 1999.
          I don't like forensic development, where I need a handbook to understand my own code, I wrote 5 years ago.

          • Re: (Score:2, Flamebait)

            by hondo77 ( 324058 )

            I don't like forensic development, where I need a handbook to understand my own code, I wrote 5 years ago.

            If you can't understand your own code five or even one year later, don't blame the language.

            • Well, if I can understand C code I wrote from 5 years ago with no trouble, and Ruby code I wrote 5 years ago with no trouble, but it is hard to read Perl code I wrote 6 months earlier, maybe it is just me. Maybe I have a Perl intolerance or something. Or maybe, if lots of other people have the same experience, there is "something to it."

              • Ah, you are right, thats it. A Perl intolerance. If I would be hit with it more often, I perhaps would join a helping group?
                I took the liberty to look at Perl 6 an hour ago. It is completely incomprehensible bullshit ... mind wanking.

                • by Cliff ( 4114 ) *

                  You will have to tell me how:

                  ^10000.grep( *.is-prime).say; # Retrieve prime numbers from 0-10,000

                  Is incomprehsible bullshit and:

                  given $value {
                  when Str { ... Do string handling ... }
                  when Int { ... Do integer handling ... }
                  when Bool { ...Do boolean handing ... }
                  default { ... Fallback handling... }
                  }

                  Is mind wanking....

                  If you've really tried the language, why not give it a comprehensive review?

                  • Rofl,
                    picking out a comprehensible part does not make the rest less mind wanking.

                    E.g. take a look into signatures.

            • Why should I not blame the language? We are talking about PERL, remember?

              It is the only thing to blame if you don't grasp what is going on ...

    • Re:Does it matter? (Score:5, Insightful)

      by DCFusor ( 1763438 ) on Saturday October 12, 2019 @07:57PM (#59301254) Homepage
      The perl 5 cycle is still slow and conservative, as it should be. Nothing I've written in a decade has been broken by a new version, but then, I don't use the nuttier stuff the instant it comes out as experimental either.
      .

      At some point, a language is done or so nearly it no longer matters if there's really a development cycle. You're supposed to be doing useful things WITH that language, not having to adapt to the tool changing underneath your feet.
      .

      This in fact annoys me as for example, the text editor (basically notepad) and calculator in linux change every release of every distro or so it seems. More often than not it's because say "gedit is no longer in development" - well bozo, maybe that's because it was finished and does its job fine now - if I want sublime text or nano, they're already there - not to mention vi or emacs..how many "simplest gui editor" versions make sense anyway?
      .

      Perhaps its just a way to keep interns busy with something they think matters while they learn to code? I for one am getting tired of having to adapt to crazy changes in what should be the simplest of tools - where did that 1/x button go? Oh, the improved version lost a bunch of features, again....Not to worry, they'll be back in a few years...
      .

      Learning a new editor is one thing. Having to re-write a big application because the language changed is NOT OK. Fine if you're a sinecure-seeking hack who needs job security just doing maintenance...I suppose.

      • For me it wasn’t so much the slow cycle of the language, but the slow introduction of Unicode and IPv6. When I had tried to participate it was hard to get a proper conversation going and trying to understand why the http library wasn’t supporting IPv6. It felt more waterfall than evolutionary. At that point I left the cathedral and walked into the bazar of more vibrant communities.

  • Either Raki or Ragú.

  • This has been going on for years.

    Then again, maybe we can now rename Python 3 to Cobra or somesuch. From where I sit the Python changes hit a lot harder than the perl changes. Then again, most of my perl is a handful of lines doing something specific, usually written 10+ years ago and not looked at since. My Python is thousands of lines making an app.

    / old stuff still Python 2
    // new stuff Python 3
    /// I retire soon, please don't burst my balloon
    • by doom ( 14564 )

      Yes, it is a bit late, but then there's no particular reason not to do it now just because it (probably) should've been done a while ago.

      Anyway: future generations should take note that it's a bad idea to name a new language like a new version. And if a project is gradually changing from an upgrade into a new system, it's a good idea to recognize where that's going as early as possible...

    • Well,
      Anaconda is already taken for some Python stuff.
      So I like the Cobra idea (pun intended)

      So, if you are retiring, do you look for a successor?

  • by msauve ( 701917 )
    Makes as much sense as renaming buy.com to rakuten.com. And by "sense", I mean fucking stupid.
  • Marketers like to rename things so they can feel like they accomplished something and feel they have something new to hype.

    Most of the time that just annoys and confuses people, and sometimes consigns something to oblivion.

    Someone will say "Ragu language" and people will go "what the hell is that?"

    At least with "Perl 6" people knew it was "that next version of Perl with an obscene amount of features that no one uses."

    "Another day, another Doug..."

    • Calling it something other than perl firewalls it away so that nobody will make the mistake of porting their perl5 code to the 'new version.'

      It's a good thing. Perl5 is finished, only maintenance is needed.

      • Perl5 is finished, only maintenance is needed.

        Nonsense.
        Release history [perl.org]
        Changelogs [perl.org]
        It's not done. But it keeps getting better and better

        • It's converging toward perfection, not morphing into something else or 'evolving.'

          • LOL, I suppose I can't argue with converging toward perfection, however, we were discussing "doneness", and new features are always being added. It is simply false to claim that it is in maintenance mode.
        • From those links you looked up but didn't read:

          Perl 5 introduced everything else, including the ability to
                        introduce everything else.

          Done.

  • Enter the lawsuits & infringements when they reach v10..
  • Yeah, I know it's Ragu, but it's close...
  • The term Raku is problematic because its pronunciation, at least in English, is not obvious. Is the a-sound long or short? Is the stress on the first or second syllable?

    • Not really. It would be rah as in rah-rah-rah, followed by coo, as in cuckoo. With an stress on each vowel.

      For it to be pronounced otherwise it would need additional letters.

  • by doom ( 14564 ) <doom@kzsu.stanford.edu> on Sunday October 13, 2019 @12:33AM (#59301820) Homepage Journal

    This is turning into a FAQ I think, To quote pvaldes (from over at reddit):

    Raku appears to be from Rakudo, the Perl 6 compiler, which is a shortened form of rakuda-dou (="way of the camel" in Japanese). Rakudo also means "paradise". The "raku" from "way of the camel" means "camel", while the "raku" from "paradise" means "fun" or "enjoyable" (or "music").

    I gather that the name of the style of pottery has interesting overtones, something like an embrace of chance results achieved by experiment... (aka "hacking"?).

    Anyway, "Raku" wasn't my favorate candidate for a new name, but I'm happy to hear that the official name-change has gone through. The previous situation was an annoyance to both the new language and the original perl it it forked off from...

    • I love the old Perl, and I'd really like Perl 6 to make a comeback... but I'm worried that apart from being ugly, "Raku" might be too close to "Rakuten," and given the latter's recent attempts to popularize their name as a brand (e.g. renaming Ebates), I would expect them to sue.

      The camel meaning is amusing, but they should have gone with a name that evokes a sense of a gemstone like Perl did. A new name might not wipe away the bad publicity, but it would at least make it easier to search for distinctly Per

      • by doom ( 14564 )

        I would've said the thing to learn from Rakuten's experience is that American's have difficulty dealing with even simple Japanese names. "Raku" wasn't my pick, but Damien Conway likes it, and he outranks me.

        One thing I will say though, since I personally dislike "Raku" there's a strong possibility it will catch on. I am not someone you want to put in charge of marketing.

  • Pascal - Modula II (Score:5, Interesting)

    by Duh-People-Really ( 6172216 ) on Sunday October 13, 2019 @01:52AM (#59301956)

    Pascal died after being renamed to Modula II, and so did Modula II, instead of Pascal vwhateveritneededtobe.

    This is signing the death knell of pearl.

    • by DrXym ( 126579 )
      Pascal wasn't renamed Modula-2. Modula-2 was a successor language to Pascal. As for why it didn't take off that is probably because Pascal was good enough and commercial implementations (e.g. Turbo Pascal) offered module like functionality and object oriented extensions.

      Pascal isn't dead yet but it has been sidelined for a very long time. In particular Microsoft Visual C++ killed development interest in Pascal on Windows. Borland Delphi offered a moderately popular resurgence when it was seen as more powe

      • by ebvwfbw ( 864834 )

        I still like pascal as a teaching language. I usually use it as a second language I teach people. After basic. Have to teach people what spaghetti code is after all.

        Then I can make them into a great C person.

    • Pascal and Modula II are completely different languages
      And as far as I am aware, Modula died and Pascal is alife and striving: https://www.freepascal.org/ [freepascal.org]

    • I was told that Pascal has been pronounced "Delphi" for the past 25 years. And I believe it, because I've been seeing it listed as a job requirement for that long. I'm not sure if I've ever seen anything called Modula listed.

  • by argStyopa ( 232550 ) on Sunday October 13, 2019 @06:59AM (#59302424) Journal

    Couldn't they have named it something a little less likely to cause market confusion like "Amazoon" or "Nutflix"?

    • I don't think it is used for any of that business-y stuff though, that has "markets" and care about "confusion."

  • I'll bite.
  • Bad choice
  • As a long time Perl user, I think this is a great solution and a rather obvious one at that. Lot of upmodded comments saying "perl6 is/will be a failure." Perl has always had a lot of FUD, some of the reductive criticism is warranted but useless.

    Python courted plebs and Perl has always been a technician's toy. Technicians aren't going to care about a name change except the practical ramifications of clearing up the compatibility issue.

    Still, it makes me wonder where all this FUD comes from. Who wants to

  • If you are not familiar with Perl6/Raku, you should take a look at it. It is really a very powerful language. The fact that it took 15 years to develop--with volunteer labor--and a few diversions along the way has hurt it in mind share among developers, but that doesn't mean that the final result is without merit. There are a lot of good Perl 6 references on the web, but most suffer from trying to do too much with the language too fast. Like many languages, you don't have to learn it all to find it very

  • Perl for all its foibles, and it had many, is still a mainstay of programming language history. Amazon was originally written in mod_perl. Lincoln Stein's torture.pl was written in Perl. Hell, the file type suffix .pl means Perl and, really, it always will mean Perl.

    When someone first handed me the Perl O'Reilly book, my reaction was, no way am I going to program in a language whose reference manual is that thick. And indeed, Perl contains many baroque constructs enough to make me wonder if Larry wall had

  • ....to rename Larry Wall into Boaty McBoatface ?
  • I guess the Japanese word for six was already taken?

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...