[John Lam:RubyCLR] Destination IUnknown, Ruby, Ruby, Ruby, Ruby SoDo (Well, NoEaDo Anyway)

by M. David Peterson

DISCLAIMER: Can you really blame me for not taking FULL ADVANTAGE of the various connections between John Lam (his personal site is IUnknown.com), Ruby (John Lam is the developer of RubyCLR), the fact that the area that used to be south of the Kingdome is called SoDo (actually, the area south of of where the Kingdome *used* to be is still there (e.g. Starbucks corporate headquarters)... But as per the video embedded below, The Kingdome is not), and a few of the lyrics behind Rancid's song Ruby SoHo**** which include "Destination unknown... Ruby, Ruby, Ruby, Ruby, SoHo?

Or maybe the better question would be, are you really all that surprised that I chose just such a title?

Pick one and go with it ;)

via a post from one of my more favorite Microsoft bloggers, Steve "Say It Like It Is, But Don't Be A Prick About It Either" Maine***, we discover that John Lam, the RubyCLR guy, has decided to take a position with Microsoft.

Dynamic Languages, Microsoft, and me

I've decided to stage a friendly takeover of Microsoft. As of January, 2007 my new work address will be Building 42 at Microsoft. I'll be working in the CLR team to help bring the love of dynamic languages out to the statically typed heathens :)

You know, maybe I need to look a bit deeper into the Ruby language... Not that I haven't played with it a bit, and not that after playing with it, I wasn't impressed, and instead that the work of the IronPython team coupled with encouragement from Sylvain, Uche, and the underlying fact that a majority of the best software developers I know at a personal level are nearly all Python developers has led me down the road to learning Python. Don't get me wrong, I *LOVE* the Python language, and when you couple IronPython + Saxon on .NET + XSLT 2.0 + XSLT 2.0 Extension Functions the result is like pure magic sprinkled with sugar.

That said, I wonder what Ruby + Saxon on .NET + XSLT 2.0 + XSLT 2.0 Extension Functions would taste like?

I bet it tastes *YUMMY* and without a doubt, soon enough... We will most definitely be finding out. :)


NOTE: To those with interest, and those willing to move forward without any documentation nor promise of *ANY* support from me, you can access the Xameleon and/or PyPod.NET Click-Once apps that provide an IronPython console with direct access to the fixed version of Saxon on .NET that allows the ability to implement .NET-based XSLT 2.0 extension functions (the current release of Saxon on .NET had a bug and as such extensions functions didn't work, but Dr. Kay fixed the problem soon after I reported it and as such, if you build out from source, it will work just fine. How do you build directly from source? How 'bout I just give you the fixed version via the Click-Once app and we call it good? That, or look over these directions I posted to the ExtensibleForge.net Trac interface a while back, check out the source from the repository, and build it doing so with the knowledge that there is *ZERO* support available (read: I wish I had the time right now to launch all of the projects I have long sinced finished out, supporting each and every one of them as a result... But, at the moment anyway... I don't, so they need to wait for release until I do.)