Linked by David Adams on Sun 7th Dec 2008 02:03 UTC, submitted by HugoS
Permalink for comment 339746
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2007-03-07
I don't think I am mistaken. The reason being that there is no obvious benefit to porting Python, Ruby, or PHP to Parrot. Not when there are already production quality versions written on top of the JVM and the .NET VM. And these implementations often run circles around their C counterparts because they can take advantage of JIT compilation and such.
I just can't see any obvious benefit to porting Python, Ruby, or PHP to Parrot. Other than "it might be fun to port it". But there's no real practical benefit.