221–230 of 257 posts
Earlier quoted context omitted.
There is no reason why it could not continue to use the exact representation and operations if it wished (and that's what FatRat does). It's just an ill-conceived concession to performance.
and yet, raku is the first serious attempt to unify Int-Rat-Num-Complex types into a cooperative Numeric space --- which I think is a good design given its untyped default approach
I am definitely a gremlin, in a specific sense: I love tools that are quirky and complicated in a way that makes me more productive. But this idea of programming in The Large vs The Small: I disagree with that comparison. A less wise person might assume that means it makes a bad language for The Large work. On the contrary, it's probably just as good as any other language at it, maybe better. The problem, as it was w…
The notion/mindset that "This tool can only be used if you are good enough" is an enormous design smell in my opinion. Tooling exist to help you and your team do the required work as good or fast as possible. If you are using tools to gate keep juniors in your field, or that are unnecessary complex in order to stroke your own ego. Then the tool is more of a weapon against the rest of your organisation instead of some…
There were so many claims in the first couple of years after Perl6/Raku's initial release in December 2015 about how it had the potential to be optimised due to its superior design but here we are nearly 8 years later and it's still takes 10 times as long as Perl 5 to parse a log file with a regex.
Yes, and those claims might have even been real (also, Perl still lags behind on Unicode stuff, or so I heard?)... the thing we like much less to talk about is that there just needs to be somebody to make those optimizations happen. Work on the actual bytecode VMs (or rather just MoarVM at this point) has been desperately lacking.
Earlier quoted context omitted.
The "Perl6/Raku is nothing like Perl 5" hype has been hugely overstated. It wasn't called Perl 6 for nothing and it was developed by the same Perl team more or less. For anyone who worked with Perl 5 significantly the legacy in Perl6/Raku is obvious. Raku's whole object model is a slightly more capable version of Moose.pm, a Perl 5 module on CPAN.
From what I heard, it half inspired Moose actually.
I am definitely a gremlin, in a specific sense: I love tools that are quirky and complicated in a way that makes me more productive. But this idea of programming in The Large vs The Small: I disagree with that comparison. A less wise person might assume that means it makes a bad language for The Large work. On the contrary, it's probably just as good as any other language at it, maybe better. The problem, as it was w…
The notion/mindset that "This tool can only be used if you are good enough" is an enormous design smell in my opinion. Tooling exist to help you and your team do the required work as good or fast as possible. If you are using tools to gate keep juniors in your field, or that are unnecessary complex in order to stroke your own ego. Then the tool is more of a weapon against the rest of your organisation instead of some…
Except that no: Many people were not even paying attention to that. And the perl sigil system - which was taught pretty much from the start - was still one of the top objections! It wasn't gatekeeping. It was people refusing to learn the tools they were meant to use.
Earlier quoted context omitted.
That's cool that's cool, but the problem is getting people to use Raku.
Or even just Raku’s grammars. Perhaps we need an RCRE library :)
Because in Raku, grammars are just a different way to write code. Grammars are really just specialized classes. And tokens / rules / regexes are just specialized methods. It all compiles down to bytecode, rather than something you can feed a statemachine.
This has several advantages: if a grammar doesn't provide functionality you need, you can write it in Raku code as part of the grammar.
It also means that when you improve execution of the bytecode, you will also improve the performance of grammars and regexes.
Finally: Raku grammars are very powerful. They are used to parse the Raku language itself. Which is a testament to its power. But also brings a whole set of challenges for the core developers :-)
> Formerly known as Perl 6. ↩ I’m in a desparate need of a message from Captain Obvious right now. I know nothing about perl
Earlier quoted context omitted.
Yes, and those claims might have even been real (also, Perl still lags behind on Unicode stuff, or so I heard?)... the thing we like much less to talk about is that there just needs to be somebody to make those optimizations happen. Work on the actual bytecode VMs (or rather just MoarVM at this point) has been desperately lacking.
Is Jonathan Worthington still active within the project? He was the original force behing optimisation if I remember.
Earlier quoted context omitted.
From what I heard, it half inspired Moose actually.
Are you sure it wasn't the Meta Object Protocol (MOP) rather than Moose? "A MOP for Perl" inspired endless debate but never amounted to much. In the end I think the Perl 5 community felt it was best left to Perl 6 but I could be wrong as this was all about 20 years ago.