This blog has personalition features for you, the reader. Below is a key of what all the icons mean and which aspects of the layout they change.
Close Window
Great job to the IronRuby team on getting this done!
This just freakin' rocks!
Wednesday, May 28, 2008 7:00 PM
It doesn't really rock.These "Iron" porting efforts just serve to bleed off resources and disappoint users.Mono has been slipping too. I see the Roadmap has been updated to push 2.0 and 2.2 releases into 2008 (originally scheduled for Q3 and Q4 2007).Look at the "amazing" success that IronPython has been.
Tom, don't be so negative. Until you have your own .NET and a corresponding Ruby, you cat try silence.
Now if only Phalanger would rename to IronPHP :-)This is just more proof that the CLR/DLR is a healthy ecosystem -- all the popular frameworks/languages are being ported over. While Java has plenty of languages (www.robert-tolksdorf.de/vmlanguages.html ), nothing beats the ease to which .NET languages can now interop.Keep up the great work!!
I think what Tom doesnt understand here is that this is about Ruby (specifically the big application RoR), not about Mono.And since he obviously does not know Ruby (else he would not think this is bad...) I wonder why he even bothers to post. I dont use RoR but I think this is great news, for several reasons.
Are you guys on drugs? A "healthy" ecoystem? There is exactly one .NET runtime that works 100%, and that is the Microsoft one. Mono is so far behind, its depressing.It is not that it couldn't be fixed, if Microsoft just opened source the core VM. There really isn't any reason not too. There are plenty of other VMs, so there isn't any amazing IP locked up in the VM. Also freely redistributable copies of all of the .NET bytecode libraries (at least the ones that don't use native code) would be nice. Isn't it retarded that the Mono guys have to re-write 15,000 .NET methods in C#, when they could just download it? Except they can't. The only free download only works on Windows. Yes, real healthy...After seeing IronPython team deliver a deliberately incomplete standard library... the "oh, you don't need the Python standard libs, as we threw in some .NET ones that only work on Windows for you... just use those." And then the whole issue about the comments from IronRuby team about how Ruby is "fragmented" and someone needs to step in and define the standard (hello? RSpec anyone?). Who should step in, do you think? Maybe just more fear about Ruby? Maybe just preparing a justification for delivering an incomplete implementation, because the IronRuby team can't figure out the spec?So far the Iron* implementations have just proven to people that are trying Ruby or Python for the first time, that these are interesting scripting languages with limited usefulness.Reminds me of Chinese democracy. Did you know China has a democratic gov't? That is what all of the chinese kids learn in school. They have 9 different political parties, so they have a democracy. A multi party system is democracy, right? Of course, it is meaningless. Just like the .NET ecosystem. If you think this is just negativity, post a link to a production website that is running Python in a .NET VM of some sort. Not some toy blog you put up on your broadband connection, but some sort of real 24x7 application. Or, better yet, some Python software that I can download and works on both .NET and CPython? I hope I can be proven wrong, but I fear I won't.It is amazing how fast everyone forgot about the J++ fiasco. The old "Java that was't Java" scam. I guess you don't need new tricks when the Internet has such a short memory.
i think the real shocker will be when someone actually deploys a rails app with iis using ironruby.right now, deploying rails with iis is next to impossible.
Wow, this has turned into a bit of purse fight.In all, I'm very happy for the IronRuby team for getting this accomplished. They based all their specification for IronRuby using the RSpec for 1.8.6. Also, in the mean time they refactored code within the DLR to make the interop between IronPython and IronRuby (and any other language) easier to implement.If some of you are concerned about getting this to work on mono, why not try it? The DLR is distributed out on CodePlex for you try.
I don't understand what all the fuss is about...I mean, its not like RoR comes even close to the awesomeness of Web Forms. It's more a language for tree-hugging type devs isn't it?D
@D'ArcyYeah, Web Forms is all you need! All this talk of MCV and stuff just makes me think that the internets (wide world web, or WWW to us geeks) is going to the dogs!
@Tom/Uhh... what?First, RSpec is for Behaviour Driven Development there hot shot - nothing at all to do with what you're talking about.If you've even spent a second in the .NET framework you'd understand the power that the CLR, and eventually the DLR, provide to developers, regardless of it belonging to a closed ecosystem like Windows.And with the introduction of IronPython & IronRuby, it will provide an existing army of developers to work in languages they'd otherwise never be exposed to, as well as provide .NET programmers with existing experience a new weapon in their arsenal to get around those spots where C#/VB simply are not the right tools."Boo hoo!" you cry - the framework doesn't work on bsd/nix - what are we to do? That doesn't disqualify .NET's existing merits, which will only be improved with more options like Python/Ruby.Should we ignore China's impressive architecture accomplishments on the grounds of their government?You are lose. Inset quarter and try again.I say bravo to the teams working on trying to interoperate these languages with .NET - it's a step in the right direction, and hopefully one that will lead to greater proliferation of .NET, especially on non-Window infrastructures.
This is really great news. The more languages that come to the .Net party the more choices I have to do each specific job. Rails is great for the front end, bit-o-linq in c# for middle tier, and a bit-o-vb.net doing XMLinq'ing for file processing in a service.(And it just as fun to turn up to RailsConf with a Vista laptop running IronRails as to turn up to a techEd with an Apple running *nix rails)
Fields denoted with a "*" are required.
