Re^5: Backend diversity for Rakudo

What matters to you Anonymity or the Discussion? It doesn't take much to understand that when you diversify, the efforts get diluted. And most of the guys even contributing to these projects Eg:Chromatic seem to agree with it. As you can already see targeting multiple backends was one of the reasons for Pugs debacle.

However regardless of all that,after reading all the threads here its not very difficult to figure out even other VM's don't have ready-made stuff what Perl 6 needs. Nor will they get it or have it, because they don't exist for Perl 6 alone. Parrot guys are more closer to Perl 6 as they started for that very reason. If parrot doesn't have a feature x then ideally that problem should be solved rather adopting a different VM. And whats the guarantee that other VM's WILL have what features you look for? Or they will get if for us if we want them. And tomorrow if we don't get it there, will we keep jumping VM after VM without covering the spec completely on none of them?

The need of the hour is spec completion, stability,speed, documentation, libraries and tools and not different backends.

Comment on Re^5: Backend diversity for Rakudo

Replies are listed 'Best First'.
Re^6: Backend diversity for Rakudo by chromatic (Archbishop) on Aug 18, 2010 at 05:30 UTC
The need of the hour is spec completion, stability,speed, documentation, libraries and tools and not different backends. Sure, but you can tell volunteers to work on only what you want them to work on until you're blue in the face, and they'll work on what they want to work on. I have a lot more confidence that Parrot will be the best host for Rakudo for the foreseeable future (and the best mechanism for cross-VM portability) than I do that some as-yet unbegun port of PCT and NQP to another VM, but that governs how I spend my time, not how anyone else does.	[reply]
Re^7: Backend diversity for Rakudo by Anonymous Monk on Aug 18, 2010 at 05:41 UTC
Your argument works great at an individual level but it is a PR disaster. At one end trying to sell Perl to world arguing about Modern Perl, regular release cycles etc. Its even difficult for others to convince their bosses/colleagues other fellow programmers about Perl 6 and its future. You tell me one reason any body sitting next to me should think about Perl 6 if he has no guarantee of seeing it come through in the near future(Unless of course the guy feels extremely passionate about it, and such need not have to convinced anyway). Perl evangelism has become fighting against a Mob these days. Regardless of whether its Reddit, HN or even other places. Ridicule, laugh and sarcasm is all you get... To make it worst we seem to live in denial.	[reply]
Re^8: Backend diversity for Rakudo by chromatic (Archbishop) on Aug 18, 2010 at 16:16 UTC
You tell me one reason any body sitting next to me should think about Perl 6 if he has no guarantee of seeing it come through in the near future.... The Rakudo compiler's 32nd monthly release in a row will occur tomorrow. Rakudo Star's second monthly release will soon follow. My conservative estimate of speed improvements is 10% over the first Star release and memory improvement appears to be 12%. That's in a month of work, and none of it the dramatic improvements we've planned. None of this is a guarantee of future results, but then again, Microsoft could deprecate the entire CLR in favor of something else, Oracle could declare Java's end of life, and Google's orbital death ray satellites could scrub C compilers from all of our systems. You decide where you put your faith.	[reply]
Re^7: Backend diversity for Rakudo by Anonymous Monk on Aug 18, 2010 at 05:49 UTC
How do the volunteers manage to do all the great stuff as you are doing? Probably a blog post will help not-so-good folks like us to get involved.	[reply]
Re^6: Backend diversity for Rakudo by szabgab (Priest) on Aug 20, 2010 at 09:24 UTC
Who is this "we" you mention? Which Anonymous does that include?	[reply]