in reply to Re^3: Backend diversity for Rakudo
in thread Backend diversity for Rakudo

Ok, whenever this word 'completion' crops up there is great deal of confusion as to what is complete.

That's correct. Which is why it's best to avoid it in a discussion about software.

Both Linux and Hurd are being actively developed, but Hurd is not complete in the same sense Linux is complete.

I see only gradual differences. And for a gradual difference it doesn't make sense to say "wait until ..."

Probably you can have a second look at the word 'Complete'.

I just took a second look. It seems half of the explanations there equate "complete" to "dead" if applied to software. So best avoid it.

Don't get me wrong, I don't love to pick on some minor language nits, but if you ask the question again without using words like "completed" or "finished", it will probably come up in a way that makes much more sense, and is much easier to answer in a meaningful way.

Perl 6 - links to (nearly) everything that is Perl 6.

Replies are listed 'Best First'.
Re^5: Backend diversity for Rakudo
by Anonymous Monk on Aug 17, 2010 at 09:59 UTC

    Thanks that you noticed the difference, However my meaning of complete was more in respect to the phrase "The complete man"

    Now does that phrase mean, "The man is dead"?. The death meaning may apply more to the term "finished" but less to "Complete". And also agree with the "wait untill.." I will use rakudo or other implementations of Perl 6 for a throw away script. But how do you expect that to be a "Complete" product for a production environment and for all such purposes where we want to sell Perl 6 to our bosses. We certainly can't sell it as a "Complete" product in the same sense we sell Perl 5 as a "Complete" product.