Summing up my thoughts about the "news" and various comments here.
1. Microsoft is being EXTREMELY stupid and short sighted if they really are dropping the Iron languages. Without dynamic languages, the .NET world becomes just one giant hammer instead of a toolbox.
2. Charles's comment about dynamic languages not fitting in with the CLR means that Microsoft should also be dropping PowerShell. Nuff said, I think.
3. Master Pie's complaints about Ruby are really complaints about dynamic languages not Ruby. While I share some of the complaints, having written a large desktop application entirely in ECMA Script, I will still turn to dynamic languages for many tasks.
Hammer and nail sort of thing, you know?
4. I have to strongly disagree about Ruby/Python mostly running on Linux. I've used many applications on Windows that are widely popular that were written in both languages. I've also done a lot of scripting on Windows using both languages. On Linux, on
the other hand, outside of those popular programs I mentioned running on Windows you're far more likely to find things written in Bash, Perl and PHP.
5. I've already disputed rhm's assertion that Ruby developers are unlikely to be using Windows, but I'll now argue about "deploying on Windows". That's hogwash. First, if it's strictly Ruby and no dependency on any .NET libraries, you can deploy to Linux
using the standard Ruby runtime. Second, if you're using .NET libraries the IronRuby platform runs on any platform that Mono runs on. And the old "Mono isn't complete" argument, that I've always found lacking anyway, really doesn't matter much here, as the
"missing" libraries on Mono are libraries that you're probably not using with IronRuby in the first place.
6. Next rhm questions whether or not .NET devs would be interested in Ruby, and the answer is emphatically YES. The .NET OpenSource folks already use tools like Rake for building, Cucumber etc. for BDD testing and there's a huge movement right now to use
Gems for package management. Then there's the whole need to allow your application to be scripted by end users and the benefits of allowing them to use any "Iron" language to do so. I could go on, but the point is made. .NET devs are already
dependent on Ruby/"Iron Languages", much less have a desire to use these languages.
All in all, if Microsoft is abandoning dynamic languages on the CLR they are screwing up massively. If they are just dropping the current Iron languages, they are still making a huge mistake, both politically and even for technical reasons.