Sponsored By Aspose - File Format APIs for .NET

Aspose are the market leader of .NET APIs for file business formats – natively work with DOCX, XLSX, PPT, PDF, MSG, MPP, images formats and many more!

Martin sends a little shot across MS’s bow

Martin Fowler on RubyMicrosoft.  Nothing I haven’t heard or said or thought before, but still, it matters when a Martin Fowler says it.

I’m going to (slowly and) carefully work up my thoughts on his post in some depth.  In the meantime, go read what Martin says and come back here and tell me what you think.  The ‘Bliki’ doesn’t do comments, but The Shade Tree Developer does (and will as long as the CS spam filter + CAPTCHA do their thing). 

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • http://www.backlinkschecker.ws/backlinks/buylinks.html Purchase High PR Backlink

    That is a great suggestion

  • http://codeprairie.net/blogs/chrisortman/archive/2007/05/31/war-is-coming.aspx Chris Ortman

    War is coming

  • http://community.hdri.net/blogs/chads_blog cmyers


    I dunno. It’s possible may become their poster child for the DLR and Silverlight, but I could be wrong.

    Man, be careful what you wish for. If I were a big Ruby fan, I’m not sure I’d want full VS.NET support (yet, at least, Orcas may hold more promise in this regard).

    W/r/t IronRuby being in CodePlex still, it seems MS is holding it at arms length and hasn’t fully absorbed it into the main fold yet. That’s probably a Good Thing(TM) as it will allow IronRuby some wiggle room without a lot of Official Process slapped down on it.

  • http://codebetter.com/blogs/jeremy.miller Jeremy D. Miller


    You know, my big question is what will the IDE experience be for IronRuby. Will MS make Ruby a first class VS.Net language? Can we also run IronRuby in purely interpretive mode for testing *and* compiled mode in production? Or do we need to look at the existing development tools.

    One way or another, I’m gonna give the IntelliJ plugin for Ruby and Ruby in Steel a spin.

  • http://community.hdri.net/blogs/chads_blog cmyers

    Fowler asks: “The big question for Microsoft’s “Iron Ruby” is how compatible will it be? Will it be a full implementation on the CLR”

    So far, trends suggest the answers to be 1.) “Completely” and “Yes”.

    IronPython, even when it was early on and still getting its feet up was amazingly compatible.

    For example, I was able to use IronPython to run Trac so that I could integrate some .NET code (web services) and not have to deal with Python … much.

    I think there was one thing that Trac did that IronPython didn’t support (and it was on their list of TODOs) so I had to code around that and modify Trac a little, but it worked, by gosh!

    So, I’m optimistic, if not confident, that IronRuby will follow the same path.

  • http://weblogs.asp.net/dstone David Stone

    I find it interesting that Martin published that on the same day that Jamie Cansdale (of TDD.NET fame) divulged all the information about his current, ongoing struggle with the VS team. [1]

    As a student, I know a huge number of my fellow students work solely on a FOSS stack. And more than a few of them are avid Ruby enthusiasts. Most of them don’t hate Microsoft, but just aren’t excited by anything coming out of Redmond. And while I /am/ excited by the new language features (Linq, Expression Trees, Lambdas etc.) that are coming in the next version of the Microsoft stack, I’ve generally lost a lot of interest in doing things the Microsoft way.

    Anyway, my point is that Microsoft isn’t just losing the alpha geeks, they’re losing future developers (or maybe I know some of the future alpha geeks…), and “hobbyists” like Jamie (although I would contend that Jamie’s an alpha geek as well).

    [1] http://weblogs.asp.net/nunitaddin/archive/2007/05/30/microsoft-vs-testdriven-net-express.aspx