Sun has picked up JRuby. Boy, you would think this dynamic language thing was important, or something. I did find two things to quibble with, one in the Ruby posting:

Will they [ed: The JRuby guys] work on JRuby full time?

Yes, but they also have a mandate to think about developer tools. Right now, developers who use dynamic languages like Python and Ruby are poorly served, compared to what Java developers have.

Perhaps Tim missed Smalltalk, which has always had superior tools.

Then, patrick Logan spotted this (via Jon Udell) from Jim Hugenin:

I'm not a dynamic language zealot, and in general I don't really understand zealots. I wrote the first three versions of the IronPython compiler in Python, but today it's written in C#. Part of the reason is that now I understand it, so the values of prototyping, and the looser thinking that really helped a lot in the early days, don't really help as much any more. Also there are now more people working on the compiler, and there are some real benefits to the static typing, and the support you can get from Visual Studio.

Well, I think Jim missed the boat there. Why? Well, it came up in Georg's talk about ObjectStudio 8 today. ObjectStudio 8 will be hosted inside VisualWorks, and the compiler (which was in C in classic OST) is now a subclass of the SmalltalkCompiler in VW. Why is that good? Because it made the whole process a heck of a lot easier: you write Smalltalk faster than C (or C#), period. It's also a heck of a lot more extensible that way. Having a language level compiler for Iron Python would have opened up a lot of cool things to developers; having it in C# just locks it away in useless-land.

Technorati Tags: dynamic+languages