Monday, March 05, 2007

Miguel de Icaza and Pixelmonkey talk Java, Mono, Windows, Linux

Andrew Montalenti, aka Pixelmonkey, started a lively debate with Miguel over at Miguel's comment google group. The thread is here, and Andrew's post on it is here.

Mono is my numero-uno interest as far as open source projects go. And I've always gotten a kick out of Miguel's style. Open source zealots seem often puzzled by Miguel's decision to dance with the devil, as they would see it.

I'm not calling Andrew a zealot, just that he brought up a number of the points that I've seen made with far less tact and forethought by some of the more zealous.

"Why would I choose mono when I have an open source java?" I think that's the wrong question. Most developers don't choose a language and/or platform. They either only know one, or of the several they know, one is dictated to them by their job. So why mono? Because it provides a path to Linux and other platforms where C# was their non-choice.

Along those lines, I'm planning on moving this blog to a mono-powered dasBlog engine on a linux host. Just to see what it's like. And to stop feeling like a *.blogspot.com poser. :)

3 comments:

Anonymous said...

Brian, seems we share some common goals. I am working to make ThinkJot V2 (full rewrite from the earlier dasBlog fork) run on Mono. I will let you know when that is complete. Btw, which dasBlog version works on Mono?
--Jes

Brian Deacon said...

Hey Jes,

Well, if you were soliciting for volunteers, it worked. :) Assuming you're willing to do a bit of ThinkJot-newbie handholding, I'm in. Expect some stupid questions coming your way soon.

Brian Deacon said...

Oh, in regards to which dasBlog version works on mono... there's a "ports" section at http://www.go-mono.com/ports/
It's a patched version of 1.4.3297.0. And looks a bit crusty, since one of the Makefiles is still using monoresgen instead of resgen. Fixing that one problem made it build fine... then that's as far as I got before the rest of reality intruded. Didn't actually fire it up to see if it worked.