3 ms·
I love Perl5, and would like Perl6 to succeed. I just don't see it happening though. It took this long for the features to settle, but now people will wait fo
by tyingq 8y ago
I love Perl5, and would like Perl6 to succeed. I just don't see it happening though. It took this long for the features to settle, but now people will wait for the performance to improve. In the meantime, the userbase has left for Ruby or Python or something else.
Interesting thread from this summer: https://www.reddit.com/r/perl6/comments/8p26bb/is_perl6_faster_than_perl_5_on_average/ https://www.reddit.com/r/perl6/comments/8p26bb/is_perl6_fast...
- Ultimatt 8y agoThat was 5 months ago. A lot happens in this space in two weeks let alone half a year. Rakudo is released monthly still, with quarterly(ish) distribution releases. An example bit of insight: https://github.com/rakudo/rakudo/search?o=desc&q=fast&s=committer-date&type=Commits https://github.com/rakudo/rakudo/search?o=desc&q=fast&s=comm... That's just the compiler rather than VM or NQP level, where you will see even more performance related work. One of the bigger breaking changes in 6.D at the language spec level is for performance of scheduling multi threaded work. https://github.com/rakudo/rakudo/pull/1004 https://github.com/rakudo/rakudo/pull/1004 The main canary test for performance used by the community is the Text::CSV module. The vanilla Raku implementation is about 2x slower than the C wrapping Perl equivalent. The nice property of the Raku library is you can run it in parallel quite trivially and then its suddenly faster than the Perl version. In general the simple introduction of hyper/race keywords into user code is a big win for performance, but perhaps not cost. There are a tonne of features of the language specific for performance most people walking through the door aren't so aware of. Native type decorating your code and variables for example, usually invokes significant improvements to numeric work. The JIT does some of that automagically but simple issues like your code implicitly switching between rational and floating point types will break optimisation. If you don't say what you really want to do Raku always assumes you want to do the safest and usually slowest thing like use bignum or rational type things, that are harder to speed up down at the CPU.
- deleted 8y ago[deleted]
- carlmr 8y ago>now people will wait for the performance to improve. In the meantime, the userbase has left for Ruby or Python or something else. Performance and Python aren't exactly related (I know you can call into C code with numpy etc., but still Python itself and idiomatic code in it is often super slow).
- gkya 8y agoI use all of the three language in my day-to-day computer usage (i.e. I have scripts in each one of them), and I don't think Python or Ruby really replaces Perl 5 at what it's doing good: being a very powerful Unix citizen. Perl 5 is still better at regexps, at string manipulation, at how it combines these features w/ Unix I/O, and at offline documentation. Ruby has the best syntax and language flexibility among all (I hate Python's significant indentation and general unnecessary "stinginess" of the syntax), and Python shines with its wide array of libraries and availability of jobs. Also, AFAIK Python supports Windows better, and has a better REPL than Ruby (Irb can not run all the code the interpreter itself can run).