Last night, Anthony Panazzo gave a talk about cloud computing to the InyAlt.NET use group.  He got some help from Jon Fuller, Mike Brown, and Shane Milton.  Shane’s not from around here (originally written for an internal company blog).

 

Jon F gave a demo using Google’s App Engine.  It got me slightly itching to dig open my “old” appegnine project from earlier this year.  I dropped it because it’s Python and Django.  I don’t know Django and I’m not excited by Python.  Personally, I believe Python is evil but not evil enough.  I’m getting picky about my languages in my old age.  But, still I was interested.

 

On the drive in this morning, I was thinking about how cold it was, but also about how if I deployed a project on Google, Mike Brown would whine about not using Azure.  He’s biased.  He’s got a website.  Not to be one to stand up to peer pressure, I began to think about the fact WebApp (Google’s default appengine library) and Django both use an abstraction calls WSGI (Pronounced Wiz-Gee).  If I could get an Adaptor to sit between IronPython and WSGI and ASP.NET, then I can have my appengine and azure it too.

 

Oh, life was grand!  I was gonna start a code-plex project and call it “bluewiskey” (Aszure + WSGI).  I was gonna write blog post called “A Year of Living Django-usly.”  But I sit now in ruins as it’s already been done.  More correctly, NWSGI is currently in development.

 

NWSGI does work, but has two big fallbacks.  It doesn’t currently support DJango out of the box (you could probably jurry-rig it).  And secondly, It currrently runs full-trust making Azure deployment an issue.  However, It’s active (a check-in from Wednesday) and the full-trust issue is being fixed.

 

Back to looking for something strange to do.  Erlang + MUD?