.net .net framework 4.0 ado.net android appengine applescript astoria beos bi c c# c++ clojure cloud clr cocoa touch concurrency couchdb cql curl data services database django dlr dynamic ef entity framework erlang exchange server full-text functional gnome go google gpu groovy haiku hpc html indexes io iphone ironpython ironruby java javascript jquery jruby jvm linq lisp lucene mac math mirah mongodb monitoring natural language nlp node.js object oriented objective-c operating systems oracle orm parallel performance podcasts powershell prototype python rails refactoring remoting reporting services ruby scripting security simpledb solr sql 2008 sql server ssrs systems programming testing tools vala vb virtualization vs 2010 web services webdav windows xml

ironruby (Friday, April 11, 2008) - for the last year i've somehow been avoiding doing any ruby work. been writing plenty of python for prototyping as and duct tape for work as well as hobby, but nothing in the way of ruby. one of the reasons i've had the opportunity to write some python is because of ironpython. no matter how much diversity i would like in my professional development the truth is

Now in IronRuby on Rails (Monday, May 17, 2010) - Just a quick note. I've again changed the architecture of this site. It's now in IronRuby on rails, running on Windows Server 2008 with SQL 2008 R2/Solr. Previously I was using django on linux with Oracle Express/Solr which was just one node in a long list of architectures I've used here. Why the change from django? Why the choice of IronRuby-microsoft-ish