Impressive List of Languages Ported to .NET Runtime

As Worf would say, most impressive.

A couple of thoughts. First, if you are designing stuff for the long term, going with one of these ports (eg a non-.NET-native language) should be considered. You always have the native runtime to fall back on. The reverse is true of C# thanks to Mono. Second, the .NET programming stack may now be officially certified as robust. Haters now dismissed, lesson over.

April 18th, 2006 | .NET, Computer, IT, Language, Microsoft, Technology

6 comments

I am indeed on 2.0. It’s nice. We’re using generics and anonymous methods in most of our stuff now, and I’m still figuring out closures.

Comment by Noel — Wednesday, April 19, 2006 @ 4:27 pm

Thanks Noel I will. O’course that assumes I finish c++ by summer and Oracle dos not buy Novell and all its assets.
Best regards

Comment by glen — Wednesday, April 19, 2006 @ 6:20 am

You can’t please everyone all the time.

Luther, the trick is to follow read the next post after following the advice of the previous one. Porting to the .NET runtime makes a lot more sense when you’re buzzed on cheap wine.

Glen, the Newsforge article is fascinating. You should check out Mono.

Comment by Noel — Tuesday, April 18, 2006 @ 11:32 pm

cool. are you on 2.0 yet? I just started at a Very Large Insurance Company, and I’m about to dive into 2.0, and I’m pretty psyched about it. who knew I could be such a geek?

Comment by bobw — Tuesday, April 18, 2006 @ 11:32 pm

I found your previous entry more practical. Also, I understood it.

Comment by Luther — Tuesday, April 18, 2006 @ 9:16 pm