From: Benoit Cerrina <benoit.cerrina@...>
Date: 2001-10-03T16:13:21+09:00
Subject: [ruby-talk:21985] Re: Let's work on Windows support


"Furio R. Filoseta (tlf.)" <furifilo901@cantv.net> wrote in message
news:000001c14b99$55e58830$d20d8a0a@mostro...
> I am just a developer, not a Guru, but it seems to me that the .NET way
> would be easier and, in the long run, better for Windows users. I am
> working right now with C# and felt I had to take a look into MSIL and it
> seems quite exhaustive to me.
>
> Given the enormous effort Microsoft is putting into .NET I think doing
> the .NET way would be all gain.

please take a look at
http://aspn.activestate.com/ASPN/NET/
this shows the result of activestate effort at porting perl and python to
..net
this is interesting and short reading (specially the Perl and Python for
..NET
Research  and perlNET things) the result is that .NET is very nice and MS
has done a loudable effort at making a language independant vm but this is
still geared at very static languages.  And it imposes its object model and
idea of inheritance it is more flexible than the jvm but may not be a nice
fit
yet for dynamic languages like python, perl or ruby.  On the
other hand building extension to allows a scripting language to tap into the
..Net library would be of a great immediate gain.

Reading stuff on jython (very similar effort but with an even more
inflexible vm)
leads me to think on the other hand that given enough effort it could work
quite nicely but it is important to try to reuse as much of the vm as
possible
and NOT write an intepreter in java or .NET.
Benoit