Post a Comment
They have a .NET runtime error they are not trapping, so all you see is the classic .NET crash screen. As an ASP.NET developer, I find that immensely funny. Always trap errors (try/catch), and a include a Custom Error Page (think "OSNews" janitor, which I haven't seen in a while!) as a fall back.
I was referring to this link:
http://plas.fit.qut.edu.au/Ruby.NET/
Edited 2006-08-09 17:51
I am learning Ruby, but first forte into programming since QBasic, and before that TRS-80 Basic, so for me this is a big deal. I was hoping to move from Ruby to C# so I could take advantage of the .NET platform, now it sounds like that transition will either be easier for me, or possibly in the future unnecesary. This, like IronPython, could also be a way to get some people who don't like scpripting languages to be willing to give them a shot. Ruby is great for a first language, and it's amazing to see how easy it is to program in. Anything that spreads acceptance, like Rails, is great news.
Anything that spreads acceptance, like Rails, is great news.
That this is just a Ruby compiler and that all those libraries aren't really there yet. Don't get me wrong, this is cool stuff, but you won't be running Rails on it anytime soon.
I believe IronPython actually has a much more complete implementation of the language libraries, but I haven't really played with that yet either.
Check out Boo (http://boo.codehaus.org) for a Python like language specifically designed for .NET and Nemerle (http://www.nemerle.org) for functional/OO hybrid specifically designed .NET
Both use static type inference, have AST macros, and have much more of an "agile" feel than Java and C#.



