From the Ruby.NET side there are only a handful of obstacles left to overcome…
This is not my impression. For example, there needs to be an
implementation of Socket. And Mutex. And another “same name” issue,
i.e. thread.rb and thread.so. And who know what.
Not to mention ADO.NET backend to ActiveRecord (like
ActiveRecord-JDBC) and other niceties. By the way, I think a lot of
Ruby and .NET integration can be developed right now, without waiting
for IronRuby or Ruby.NET, by using RubyCLR which has no compatibility
problems.
Thanks! I’ve updated the post and integrated your comments inline to
the
post where applicable.
since I really do need an excuse to blog these days
Oh, I’m sure you’ve just got just oodles of time on your hands these
days,
huh?!
Well, since you’re obviously looking for things to do with the extra
seven
seconds you have each week to work on “side” projects ;-), before I
forget
http://ironruby.net still points to the GoDaddy default parked page
where as http://www.ironruby.net properly points to your server. Not a
huge thing, but seems worth pointing out.