Linked by Thom Holwerda on Tue 7th Jul 2009 08:51 UTC, submitted by PLan
Mono Project We've already seen some heavy discussion on Mono and C# here on OSNews the past few weeks, as it became clear the patent situation regarding the ECMA parts of Mono was anything but faith inspiring. This issue seems to be resolved now: Microsoft has made a legally binding promise not to sue anyone who uses or distributes implementations of said ECMA standards. Following this news, Mono will be split in two; the ECMA standard parts, and the rest.
Thread beginning with comment 372059
To view parent comment, click here.
To read all comments associated with this story, please click here.
stanbr
Member since:
2009-05-22

Technicly speaking, you could use other languages to develop for the JVM too. It may not be that easy (since the JVM was not made from ground zero to be multi-lingual) but It can be done, and there are some compilers around. Some real examples are listed here: http://www.is-research.de/info/vmlanguages/?s=compile

So if what we need is a VM where wecan use many languages, we could create our own or extend JVM or some other VM. No reason to jump to a "not-so-open" solution created by evil itself.

Reply Parent Score: -1

sukru Member since:
2006-11-19

I know about that (except for the "created by evil itself" part).

For example IronPython (and DLR) has been done by Jython creator (Jim Hugunin) - who is now working for Microsoft btw. So you can do many stuff for JVM, too. (I think there was lisp for JVM, too).

Nevertheless, MS has added support for special constructs that made the VM flexible enough for many languages (e.g: I can directly use Pytho standard lib sources from CPython in IronPython without any modifications):

* Generics in the VM itself
* Extensive metadata
* Faster reflection based calls (from .Net 2.0)
* Nullable type support for the VM
* Several functional language constructs
* DLR (is actually an open source extension, but utilized by Python, Ruby and JavaScript implementations).

So, basically, MS did look at where Java fell short, and also at their own mistakes (like VB), and did a good job. And it helps me with my project, double kudos to them.

Edited 2009-07-07 11:40 UTC

Reply Parent Score: 4

stanbr Member since:
2009-05-22

So lets do the same. Lets see what are the advantages of .NET, the problems, and lets try to create or extend what we have with this new ideas. And not abandon everything to start over. If we abandon what we have everytime something new appears, we have a big problem ;) Speacily if these include us losing (some of) our freedom.

Reply Parent Score: 1