Neither trying to convince you nor claiming that I am.

I hope this was already clear.

Update

And if your last status is from 2011 then you should certainly watch the 2019 videos and comment on them.

And if your last status is from 2011 then you should certainly watch the 2019 videos and comment on them.

Sure, my information is a little out of date, but it seems like the argument has been consistent since 2011. "Performance improvements are inevitable and imminent". That wasn't obviously true to me in 2011, and it's not obviously true to me in 2019.

I've written elsewhere a little bit about the architectural differences between Parrot and Moar and my concerns that Moar has made some of the same mistakes that Parrot did (and ignoring some of the experiment and design work that Parrot was working on). Nothing I've seen since then has made me think that Rakudo can get the order-of-magnitude speed improvements in the large that it needs to outperform Perl reliably overall or that it can get the multiple order-of-magnitude speed improvements in the large it would need to outperform JavaScript or other well optimized JIT/AOT language implementations.

But, as always, I could be wrong.

> But, as always, I could be wrong.

Even worse, now you need to elaborate why you're sure that it's a lost cause and add arguments to your critic.

Of course you could watch the videos first and tell us afterwards where the logical fallacies are. This might be easier.

This whole underdetailed "nothing I've seen till 2011" routine is little convincing and won't help you getting detailed answers to your (rhetorical?) question. :)

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}