Podcast #61

Article hero image

In this episode of the podcast, Joel and Jeff sit down with Miguel de Icaza of the Mono project to discuss Mono, Silverlight / Moonlight, and the pros and cons of open sourcing your code.

  • Miguel is one of the lead developers on the Mono project, which is an ongoing effort to bring the .NET framework to Linux and other non-Microsoft platforms.
  • Miguel characterizes Silverlight (known as Moonlight on Mono) as "the good parts" of WPF. It's a newer way to build a cross-platform GUI app, an alternative to GTK and Windows Forms.
  • A brief discussion of the implications of cross-platform GUIs, which lack that native flair. Do you have the manpower to maintain three distinct versions of your GUI application -- one for Mac, one for Windows, and one for *nixes? Do only programmers notice the subtle differences?
  • Revisiting Fitt's Law, and applications and operating systems that don't make good use of it. Certain areas of the screen, mostly the top and bottom and to a lesser extent the sides, are infinitely large, and should be used prominently in the UI to leverage Fitt's Law.
  • Mono runs on the iPhone, through the Unity game engine! This was challenging for the Mono team to develop, because interpreters and runtimes are explicitly disallowed in terms of the iPhone SDK. Mono had to be converted from a JIT to a static compiler.
  • Per Miguel, programmers wanted Mono because Objective-C is fairly primitive in memory management and requires a lot of repetition and boilerplate. With Mono "this is all taken care for you", as a higher level language.
  • Due to concerns within the free software community, Microsoft made a legally binding promise that it will not enforce patents against Mono -- for the core framework.
  • It turns out that the Microsoft Office 2010 web component, which is free for consumers, is 100% JavaScript + HTML. If Silverlight wasn't required to pull off Office-in-the-browser by Microsoft itself, is Silverlight really necessary in the bigger scheme of things?
  • Miguel divides the world into PutPixel Programmers and printf programmers. Which type are you?
  • Some big game projects that use Mono for scripting: Second Life, and The Sims 3. Also, a very large social networking site I can't mention by name was recently ported to Mono.
  • One of my long term 5 year goals is for the Stack Overflow discussion engine to become a go-to choice for public internet discussion, on par with phpBB and its kin.
  • Miguel offers his insight into the controversial discussion of whether open sourcing Stack Overflow would destroy our business model.
  • We actually have contributed one open-source component of Stack Overflow back to the community -- the Javascript WMD editor. Also, we provide all of our question and answer content back to the community licensed as cc-wiki.
  • Our Stack Exchange hosted solution will offer free versions for non-profit organizations, and we're also looking at provided an ad-subsidized version of it as well.
  • Miguel de Icaza is also a Stack Overflow user -- with 22 answers and 3,484 reputation.
  • Check out the Mono Migration Analyzer, which will tell you how easily you can (or can't) port your .NET project to Mono and run it on other platforms. Please do, because feedback from this tool is used to prioritize future Mono development!
  • Miguel committed to speaking at the Boston Stack Overflow DevDays and presenting some of the same Mono goodness he talked about here.
  • In other Stack Overflow news, the Super User semi-public beta is now open. Come join us!

Our favorite Stack Overflow question this week:

If you'd like to submit a question to be answered in our next episode, record an audio file (90 seconds or less) and mail it to podcast@stackoverflow.com. You can record a question using nothing but a telephone and a web browser. We also have a dedicated phone number you can call to leave audio questions at 646-826-3879.

The transcript wiki for this episode is available for public editing.

Login with your stackoverflow.com account to take part in the discussion.