2009 may not be the year of Linux on the desktop, but surely can be appointed as the year of Mono.
David Siegel, creator of GnomeDo felt constructive enough to share 5 easy steps to create a viable alternative to Mono.
- Create a mailing list where people interested in replacing Mono and/or Mono-based applications can subscribe. A quick perusal of Google Blogsearch, Reddit, Digg, and Slashdot will turn up many vociferous individuals who appear to be willing to contribute. These people need to start working together instead of participating in the same fruitless arguments over and over again.
- Interview stakeholders. Figure out why developers like me are using Mono; I love Mono and would be happy to tell you why.
- Conduct a competitive analysis, evaluating Mono and technologies like it. Look at C with GObject, Qt, Etoile, GNUStep, Squeak and others. Document the strengths and weaknesses of these tools for creating Linux applications. How complete are they? Are they actively developed? Why do developers pick them? Why are they popular or unpopular?
- Using this competitive analysis data, decide on the best existing alternative to Mono.
- Using the data about why developers choose Mono, begin to address the deficiencies in the chosen alternative. The mailing list subscribers from step 1 should be eager to help — get them involved writing documentation, reference applications, libraries, and new language features.
It’s disappointing to see how much David misses the point. Other than marking everything against Mono as non serious, he just tackles the technical issues under this premise:
Recently, the noisy debate over whether Mono poses a real threat to Linux has gotten even noisier. I’m not a lawyer so I’m not going to comment on matters I don’t fully understand
Maybe he’s right when he says that people who don’t like Mono are not organized enough. Should we create some drawing ? Will that help people to understand ?
*** The issue with Mono is not technical ***
Sure we’d love to interview you coding starlettes about how much you like the beloved Mono, and yes, create mailing list and all that stuff. And stop talking about it and hey! creating a new language to replace it (how nice. Btw Vala, anyone ?)
But, ultimately, those 5 steps are just 5 ones to flip a burger and shift the discussion from the licensing side, to the technical side.
But here’s the good news, I feel constructive enough to give the Mono community 1 easier, single step to get everything done. And if you do, you can keep the Mono (how cool!).
Pressure Novell and Microsoft (as some of you work in both the companies) to change the agreement to look like this:
Subject to the terms and conditions of this License, Google and its affiliates hereby grant to you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this License) patent license for patents necessarily infringed by implementation of this specification. If you institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the implementation of the specification constitutes direct or contributory patent infringement, then any patent licenses for the specification granted to you under this License shall terminate as of the date such litigation is filed.
Is that easy. Everybody wins. Even Microsoft.
If you don’t, don’t expect concerns to go away anytime soon. Doesn’t matter what the Ubuntu policy is, that’s not just a Canonical issue. It’s everybody’s.
2012 will be an interesting year. Then we laugh.