3 ms·
I think this article is reading way too much into the issue. I'm guessing Microsoft canned IronRuby because there weren't enough people using it to justify the
by sordina 16y ago
I think this article is reading way too much into the issue. I'm guessing Microsoft canned IronRuby because there weren't enough people using it to justify the continued development required to keep up with the canonical version.
- cageface 16y agoCompletely agree. I also completely disagree with the author that it's in Microsoft's best interests to handcuff its developers to its platform. That strategy might have made sense when Microsoft was still the 800lb gorilla lording over the entire market. Now that they have some real competition they're going to have to compete like everybody else: by making the best products they can that people use by choice. If anything they've clung to their old monopolies so long that they've seriously jeopardized their future.
- marksmen 16y agoI feel C# is one of the best languages out there second only to python. Also Python works extremely well on windows and more than 99% of the packages support windows. dunno may be ruby programmers are apple fanboi's
- latch 16y agoIt isn't like Microsoft made it particularly easy for developers to use IronRuby though. Look at these two popular Connect issues to have IronRuby and IronPython integrated with VS 2010: https://connect.microsoft.com/VisualStudio/feedback/details/475830/ironpython-integration https://connect.microsoft.com/VisualStudio/feedback/details/... http://connect.microsoft.com/VisualStudio/feedback/details/479957/ironruby-integration-in-visual-studio-2010 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.