A Snowball's Chance In Hell : IronRuby
openmymind.net
openmymind.net
Its dubious to say that in the face of Windows and Office, Ruby is not worth investing in - in the face of windows and Office, NOTHING is worth investing in.
This is a common business trap - why spend money on insignificant businesses when you already have giant product lines - that many companies fall into. Microsoft has already done it with Windows Mobile and IE, and is trying to avoid the same fate with its ZuneOS and Cloud Computing offerings.
A company caught in a local maximum might really be unable to escape the situation, in that the purse holders are simply unwilling to open the purse for investments on a scale necessary to get into a different position. And they have a point.
"You want to take these golden goose eggs and invest in diamond mining? No, we keep the goose eggs, that's what they are there for!"
IE, companies don't exist a priori to grow and grow. A company exists to grow, become profitable and return the profits to the owners hot little hands.
"in the face of windows and Office, NOTHING is worth investing in." - that might indeed be true. And it might the case that the only thing MS really is throw enough money at different project to keep from seeming like the abusive rent-extractor that its market position makes it.
http://rubyinstaller.org/ would care to disagree. It's just that it's included by default on many Unixes/BSDs (/GNUs/what-have-yous). Windows includes utterly squat for development of any kind on a fresh install; the exact same statement could have been made for any language.
Literally. You can't compile C out of the box either, nor any .Net code. Does that mean nobody programs in C or .Net on Windows?
That being said, I concur that they are bad options, ugh.
Still, it is a fairly academic argument since notepad + command line is a pretty poor dev environment in any os.
At Euruko 2008, I chaired the evening panel and brought it up too. A room of 400 people went to silence when I asked if Windows support was considered important to Rubyists.
If anything they've clung to their old monopolies so long that they've seriously jeopardized their future.
https://connect.microsoft.com/VisualStudio/feedback/details/...
http://connect.microsoft.com/VisualStudio/feedback/details/4...
While its sad that it takes IDE integration, the truth is that it really does and that Microsoft knows it. So its hard to say it didn't have the enough people using it, when they never did the 1 thing they really had to do to give it a chance.
BTW Windows is completely useless for any serious Ruby development/hosting. There are a ton of bugs in networking, threading, GC.
Having languages that can be used on both sides of the fence breeds a generation of developers that can jump the fence anytime. This is death for them. They will never encourage it.
So I don't get their problem.
It would be interesting to have a WinGlade/WPFGlade GUI library that used the GUI descriptors Glade generates to build native Windows interfaces on-the-fly. That would make life very easy for porters. It's so interesting I find it unlikely I am the first to have this idea. Got to google it.
Would be even funnier to have a plugin for Visual Studio to "Save As Glade"...
For big companies to survive long term, the main thing is to have the flexibility to do that. The most relevant example here is IBM, which almost didn't survive the 80s until they emphasized more system integration.
As humanity progresses, demands will change. Microsoft has enough power, both in terms of number of employees and in cash, to pursue more than one option. Hence, many of the innovation coming from Microsoft Research can be very useful in the future. Moreover, one of the main advantages for Microsoft in the 80s and 90s was that they are friendly to developers. Of course there will eventually be a tie-in. You start using IronRuby, then you find ready .Net solutions to your programming, then you commit to using their database, and maybe visualisation via Excel, and you find yourself and your customers tied to the Windows/Office platform. Just like many companies are tied to IE6 despite what Microsoft wants and despite common sense.
Give developers no incentives at all, and they wander around. At some point, the clear division in tools makes people either commit to Microsoft or to everything else, and when Windows come short (and it will, nothing is forever) people will move in droves. But give them a semblance of cross compatibility, and they will stick to Windows/Office while convincing themselves that there is always a way out. In reality, they will be locked by the economics of rewriting all the use of .Net technologies.
Bad for the community, because splitting the community into Microsoft and others camps will lessen competition in both sides. Cross pollination will C# and Ruby will not exist when there is no shared community. And no improvements will be needed in either camp because of new features in the other.
Now it's obvious why IronRuby was relicensed under the Apache License just a few weeks back.. no-one would have bothered picking up the reins if they hadn't.
The world you would live in is full of sycophants. The only people you'd have talk about XYZ would be people who love XYZ. You would dismiss anyone who thinks better alternatives exist.
Q: "Hey, isn't this antenna problem awesome?" A: "It ROCKS!!!! Its like a super cool game!"
Q: "Dude, don't you love how this page doesn't render well in IE?" A: "Oh Man, we get to play with HTML and CSS for the next hour!"