From: "James, Roshan (Cognizant)" <JRoshan@...>
Date: 2004-04-22T18:01:18+09:00
Subject: Re: Ruby on .NET (was Re: A Ruby WishList)

------=_NextPartTM-000-b0cf6075-2cb3-4d18-8d20-0dea8cc52c54
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

//_I_ am not going to write an interpreter on .NET (nor on=20
//Parrot) but anyone else can.
//
//In the future, people may use Ruby on .NET or Ruby on Parrot=20
//daily, and my interpreter would be a reference implementation.
//
//							matz.

Accepted Matz. It would also be unfair that everyone brings their
problems to you and you are expected to keep solving them. I am looking
forward to the ideas you put into Rite.=20

Maybe sometime Rite itself can be extended to bridge to .Net, such that
Ruby is its best under Rite and the interop bridge is the only slow
link. Sometime when you have designs for Rite available I would really
like to see the features the runtime offers.=20

I however request you to put up reasons why Ruby wasn't targetted for
the CLR sometime - even if that reason was simply 'I want to enjoy
writing my own VM'. There is a reason why I am asking you for this.
There are people at MS and ouside who are serious about getting the CLR
(or CLI) to provide better support for functional and dynamic languages.
Having a solid set of cases againt Ruby running on the CLR could direct
sufficient research in that direction, which on the whole is a good
thing.=20

Two things that bother me -=20
1) IronPython : Python on the CLR=20
	<http://www.hole.fi/jajvirta/weblog/20031210T0901.html>
2) Groovy : A ruby like language on the JVM=20
	<http://groovy.codehaus.org>


You have my respect.
Roshan
http://pensieve.thinkingms.com

------=_NextPartTM-000-b0cf6075-2cb3-4d18-8d20-0dea8cc52c54
Content-Type: text/plain;
	name="InterScan_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="InterScan_Disclaimer.txt"


This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. 
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly 
prohibited and may be unlawful.

		Visit us at http://www.cognizant.com


------=_NextPartTM-000-b0cf6075-2cb3-4d18-8d20-0dea8cc52c54--