News for hackers. Stuff that matters.
Re:Raku Perl 6.d [pdf] by kbenson on Monday November 05, 2018 @11:51AM (#18383792)
This is an interesting bit that HN seems to discuss a lot:

Some community members believe "Perl 6" is a very confusing name: it uses a digit as part of the name and it conflicts with the name of a sister language "Perl". Some outsiders don't realize "Perl 6" is a brand new language—vastly different than "Perl"—and so avoid it, thinking they know what it is already. At the same time, some who love "Perl" come to "Perl 6" and feel tricked, because the language isn't the next release of that language, but an entirely different one.

To clear up the confusion, Larry Wall created a second name for the language, a "stage name" if you will. That name is "Raku". It can be used interchangeably with the original "Perl 6" name or even be combined with it to form "Raku Perl 6". Pick the one that works the best for you and use it consistently

Re:Raku Perl 6.d [pdf] by 3rdAccount on Tuesday November 06, 2018 @06:06PM (#18395687)
I've been in hundreds of P6 conversations and it is always such a bummer to see that this is always the number 1 thing discussed. Not the merits of the language, not the grammars, or concurrency, MOP, functional and OO syntax, junctions, running multiple languages, gradual typing, restricting inputs with types, Unicode....none of that.

The fact that it is always brought up to me makes me think they should've just called it something entirely different. Hindsight is 20:20 though.

Re:Raku Perl 6.d [pdf] by s_kilk on Wednesday November 07, 2018 @06:15AM (#18398414)
> Hindsight is 20:20 though.

Well... a lot of folks saw this coming. As you say, it's been brought up again and again, since the start. Foresight is also 20:20, if the right people are willing to listen to what's being said.

Re:Raku Perl 6.d [pdf] by justinator on Tuesday November 06, 2018 @05:55PM (#18395636)
This is such a blunder in naming in a line of blunders that is this language. So we have,

* Perl 6 * Raku * Raku Perl 6

and we're told to, "Pick the one that works the best for you and use it consistently". And don't forget there's,

Rakudo, a compiler for Perl 6 -aka- Rakudo Perl 6 Compiler

If you wanna rename things, fine - just do it, don't do this halfsies thing. Don't make the name collide with something else, especially in a very related project.

Re:Raku Perl 6.d [pdf] by kbenson on Tuesday November 06, 2018 @06:24PM (#18395781)
My initial thoughts were womewhat similar. Raku when there's already a Rakudo? I guess the reasoning is that they don't want to impart some special status to Rakudo, but they might as well if it's this close. For the last few years I've actually been of the opinion that if they were ever going to change the name, making it Rakudo would make the most sense. Just make Rakudo the reference implementation of the Rakudo language (the language formerly known as Perl 6), and call it a day.

Actually, the more I think about it, using "Rakudo (the language formerly known as Perl 6)" as a descriptor would probably do the best job encapsulating what it is succinctly. It was a continuation of Perl, but now it's its own thing. As opposed to "Perl 6", which doesn't really convey how radically different it is.

I'm not really one of the "Perl 5 needs to reclaim the Perl 6 name" camp, even though I'm a full time Perl developer and have been for close to two decades. Perl 5 will do what Perl 5's going to do, and freeing up the Perl 6 name won't help all that much with that (it's not like there's enough changes worth making a Perl 7 from, and a purely marketing driven name change would just be laughed at). It might actually be more beneficial to Perl 6.

Re:Raku Perl 6.d [pdf] by justinator on Tuesday November 06, 2018 @07:06PM (#18396065)
I think it's also time to just call it on Perl 5: It's a dead end: no one can work with the internals unless you're a wizard, and getting the porters to decide on any large features is impossible (function signatures, anyone?), and the, "experimental" pragma is broken.

Is it still useful? Damn right it is, but there's not going to be a Perl 5++.

Speaking as someone who's been writing Perl since oh, 1997 or so. So another multi-decader (and no plans of stopping) - where do we all meet? At the bar?

Re:Raku Perl 6.d [pdf] by smueller1234 on Wednesday November 07, 2018 @04:33AM (#18398053)
I don't think working on the perl5 internals is quite as hard as you make it sound. Yes, there's brittle dependencies between many parts. Yes, it's a very complex piece of software (and in intrinsic and implementation specific ways). But the single biggest barrier for Perl devs to hack on it is that most of them aren't also great C programmers. To wit, I'd tried many times to get the hang of it as a Perl dev and struggled. After I learned C properly for unrelated reasons, the nextb attempt went swimmingly. I've also seen folks show up on the porters list and get up to speed in just a few weeks.

Now, I'll concede the point regarding language design though: the Perl 5 Porters have become very conservative wrt language evolution. I used to be highly skeptical of this (I convinced folks of strict by default in 5.12 and oh how much I lobbied behind the scenes for fully @_ eschewing function signatures!) but since we made a number of blunders in such changes in the decade prior, I understand the conservativism.

Re:Raku Perl 6.d [pdf] by justinator on Wednesday November 07, 2018 @02:09PM (#18401381)
I don't mind conservative changes to the language honestly. Knowing that what you get is what you get is quite empowering. But I'm not going to confuse and lie to myself into thinking there's going to be massive new features in any new version of Perl (5). That's what Perl 6 was supposed to be, but "Perl 6" isn't Perl and that's not a great thing, as choices to add to my tool box just puts Perl 6/Raku in line against Python, Ruby, Scala, Java, etc, etc, etc. I'm not saying anything new... that's the existential crisis created by not having backwards compat. Does Perl 6/Raku seem AWESOME?! Yeah; but not production-ready.

The idea of extending things via modules in Perl 5 was a great one, but there's a limit on what you can without features guaranteed to be in core. I also get the idea that keeping the core small is probably a good one (by not shipping every module in the world), and keeping the language opinionated (by letter you select just what type of meta-object system you want, but after a while, it doesn't seem like these things help with architecting a future for the core language.

So it goes, I suppose.

Re:Raku Perl 6.d [pdf] by cygx on Wednesday November 07, 2018 @10:38AM (#18399795)
Rurban is working on modernizing Perl 5, eg http://perl11.org/cperl/perlclass.html

It is doubtful this will ever be backported into the official distribution, because $drama...

Re:Raku Perl 6.d [pdf] by rurban on Wednesday November 07, 2018 @05:34PM (#18402956)
It will not, given the current culture war, but perl5 will just die off, and cperl is the replacement. esp. when it will be 2x faster.
Re:Raku Perl 6.d [pdf] by psergeant on Wednesday November 07, 2018 @04:39AM (#18398076)
mst doing some interesting work with babble, a babel for Perl 5. Hoping we get a typescript workalike in Perl.
Re:Raku Perl 6.d [pdf] by haolez on Tuesday November 06, 2018 @06:03PM (#18395678)
It might be a good idea, regardless of the confusion that this can cause in the short term. Do you have any suggestion of a better "fix", apart from choosing a more appropriate name at the time of its inception?
Re:Raku Perl 6.d [pdf] by justinator on Tuesday November 06, 2018 @06:13PM (#18395725)
"Raku" sounds fine with me - just rename it. Deprecation time where the name is known as, "Kaku (formerly: Perl 6) for the next year until Raku.e (or whatever they call it) comes out.
Re:Raku Perl 6.d [pdf] by zeade on Tuesday November 06, 2018 @07:29PM (#18396189)
This sounds exactly like a Larry Wall solution, especially the "use interchangeably" and "pick the one that works the best for you" parts.
Re:Raku Perl 6.d [pdf] by petre on Wednesday November 07, 2018 @03:11AM (#18397735)
I like Larry Wall solutions. Why just throw away a perfectly working implementation when people are still using it and maintainers are still motivated to work on it? Why not do a new spec which improves on the old one and if it's succesful people will switch anyway. It allows the language to evolve while it also doesn't force users into the new thing against their will. None of that "Python 2.7 is going to be EOL in 1/1/2020".
Re:Raku Perl 6.d [pdf] by bionoid on Wednesday November 07, 2018 @05:16AM (#18398205)
> I like Larry Wall solutions.

Me too, historically anyway, but I'm not a fan of this half-way approach. Someone explicitly requested that Larry create an alias for the language [0].

> If another name is truly as superior as the full-rename proponents claim it would be, I believe the alias can become a defacto name through its sheer amount of use. Thus, the creation of the alias can be seen as a means for the full-rename proponents to prove their claims.

Emphasis mine. Among other things, this does not compute for me. Adopting three names for the language (Raku, Raku Perl 6, Perl 6) is the exact opposite of what the full-rename proponents are suggesting. You're not giving them an opportunity to prove their claims, you're giving them the middle finger. Or that's how it seems to me, anyway.

[0] https://rakudo.party/post/A-Request-to-Larry-Wall-to-Create-...

Re:Raku Perl 6.d [pdf] by petre on Wednesday November 07, 2018 @07:54AM (#18398769)
Perl 6 is still Perl and the name was in use for quite some time, so an alias makes better sense rather than a full rename. Full renames are annoying. Just look at ECMAScript. Is anyone using this name? No, everybody's still using JavaScript. People are only using ES5/6/7 when they refer to the specification. The name stuck. It's too late now. And people are needlessly wasting too much energy over a name.

“There are only two hard things in Computer Science: cache invalidation and naming things.” -- Phil Karlton

Re:Raku Perl 6.d [pdf] by s_kilk on Wednesday November 07, 2018 @08:55AM (#18399077)
The difference is that Javascript is outrageously popular, while Perl 6 is confined to an audience of a handful of nerds (me included). I think this is a great time to just switch names, as the number of people affected is tiny.
Re:Raku Perl 6.d [pdf] by cygx on Wednesday November 07, 2018 @10:41AM (#18399814)
There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
Re:Raku Perl 6.d [pdf] by fasquoika on Tuesday November 06, 2018 @07:52PM (#18396295)
"There's more than one way to name it"