<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Five straightforward steps to vanquish Mono</title>
	<atom:link href="http://davidsiegel.org/five-steps-to-vanquish-mono/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidsiegel.org/five-steps-to-vanquish-mono/</link>
	<description>David Siegel</description>
	<lastBuildDate>Thu, 04 Mar 2010 01:16:34 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anti Torben Brosten</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1915</link>
		<dc:creator>Anti Torben Brosten</dc:creator>
		<pubDate>Fri, 20 Nov 2009 11:13:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1915</guid>
		<description>Please, the question about patents is ok (at least theoretically possible or may be not I dont know).

But if you tell Mono a Closed Source SDK, you have absolutely no plan what it is.

And I think what poeple really like is C#. And the &quot;plain&quot; approach --&gt; a Language of your flavor,  a compiler, and the CLI. You don&#039;t need anything more.

Mono is just a framwork build on top of it.

There arent much languages out there which can really be compared to it (to be honest, I like the new version of java). But C++ and Python and completly different.

But JAVA was to restrictive in the past (my opionion).</description>
		<content:encoded><![CDATA[<p>Please, the question about patents is ok (at least theoretically possible or may be not I dont know).</p>
<p>But if you tell Mono a Closed Source SDK, you have absolutely no plan what it is.</p>
<p>And I think what poeple really like is C#. And the &#8220;plain&#8221; approach &#8211;&gt; a Language of your flavor,  a compiler, and the CLI. You don&#8217;t need anything more.</p>
<p>Mono is just a framwork build on top of it.</p>
<p>There arent much languages out there which can really be compared to it (to be honest, I like the new version of java). But C++ and Python and completly different.</p>
<p>But JAVA was to restrictive in the past (my opionion).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torben Brosten</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1541</link>
		<dc:creator>Torben Brosten</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1541</guid>
		<description>Another reason to avoid any closed-source SDK: If the SDK changes features and your software will not build on the newer SDK version, you may have to re-write the portion of your software that depends on the broken SDK.

This happened to me when MS stopped supporting and dropped MS Macro Language in Excel for Visual Basic. Apparently MS had Excel stop supporting macros to force developers to upgrade.  My project didn&#039;t have the funding to re-write, so the thousands of lines of code became useless with little warning.  After 2 years, MS began supporting macros again, but by then, the project (and business) was dust.  If this had been an open-source language, I could have forked the project, if only locally. Live and learn: I won&#039;t depend on closed-source SDKs again.</description>
		<content:encoded><![CDATA[<p>Another reason to avoid any closed-source SDK: If the SDK changes features and your software will not build on the newer SDK version, you may have to re-write the portion of your software that depends on the broken SDK.</p>
<p>This happened to me when MS stopped supporting and dropped MS Macro Language in Excel for Visual Basic. Apparently MS had Excel stop supporting macros to force developers to upgrade.  My project didn&#8217;t have the funding to re-write, so the thousands of lines of code became useless with little warning.  After 2 years, MS began supporting macros again, but by then, the project (and business) was dust.  If this had been an open-source language, I could have forked the project, if only locally. Live and learn: I won&#8217;t depend on closed-source SDKs again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1464</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 07 Jul 2009 07:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1464</guid>
		<description>The reason I use Mono is because it combines a safe high-level language with low-level features, C interoperability, good development tools, and bindings to all the standard open source libraries.  Oh, and Mono has a large developer and user community, in part because of its overlap with .NET

The only language that even comes close right now is &quot;D&quot;, but &quot;D&quot; is a niche language with a small community.  Another platform that might replace Mono is LLVM, but that, too, is a long way off.

I have yet to see a convincing legal argument against Mono.  All the claims of patent threats seem like FUD to me.

More importantly, anybody wanting to replace Mono with something else needs to go further than merely providing a better technology: they need to come up with a reasonable strategy to make that language mainstream.</description>
		<content:encoded><![CDATA[<p>The reason I use Mono is because it combines a safe high-level language with low-level features, C interoperability, good development tools, and bindings to all the standard open source libraries.  Oh, and Mono has a large developer and user community, in part because of its overlap with .NET</p>
<p>The only language that even comes close right now is &#8220;D&#8221;, but &#8220;D&#8221; is a niche language with a small community.  Another platform that might replace Mono is LLVM, but that, too, is a long way off.</p>
<p>I have yet to see a convincing legal argument against Mono.  All the claims of patent threats seem like FUD to me.</p>
<p>More importantly, anybody wanting to replace Mono with something else needs to go further than merely providing a better technology: they need to come up with a reasonable strategy to make that language mainstream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1402</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 06 Jul 2009 23:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1402</guid>
		<description>Brett, you&#039;ve summed up my career -- I interned for Google working on Google Talk, and worked for Idealab for a year and a summer, and now am at Canonical.

Brett, Nathaneal, I have another post on this blog about the decision to use Mono. I decided on it by a process of elimination, after exploring writing Gtk+ apps in C, Python, Vala, Java, Boo, Haskell, Clojure, and OCaml. I am kind of a PL weenie and I know many languages, so I implemented basic Gtk+ examples in most of those languages (the ones that had Gtk+ bindings in a reasonable state) and found that C# on Mono gave me a statically typed language, pretty good performance, tons of support, preexisting applications to learn from, well maintained documentation, bindings, and libraries, and published books on .NET/C#/Mono.

At first, I viewed C# as merely a better version of Java and became a bit bored with the language about a year and a half ago. I started writing a lot of Haskell, and C# just didn&#039;t seem fun enough to warrant coding in my spare time. After C# 3.0 came out, I fell in LOVE with the language -- LINQ, lambdas, and type inference made it really easy to do the kind of higher-order programming I thoroughly enjoy. Microsoft Research employs a group of really brainy PL researchers like Eric Meijer and Simon-Peyton Jones, so a lot of functional features from languages like F# and Haskell are making their way into successive generations of C#. It really is a cutting-edge language in mainstream language clothing :)</description>
		<content:encoded><![CDATA[<p>Brett, you&#8217;ve summed up my career &#8212; I interned for Google working on Google Talk, and worked for Idealab for a year and a summer, and now am at Canonical.</p>
<p>Brett, Nathaneal, I have another post on this blog about the decision to use Mono. I decided on it by a process of elimination, after exploring writing Gtk+ apps in C, Python, Vala, Java, Boo, Haskell, Clojure, and OCaml. I am kind of a PL weenie and I know many languages, so I implemented basic Gtk+ examples in most of those languages (the ones that had Gtk+ bindings in a reasonable state) and found that C# on Mono gave me a statically typed language, pretty good performance, tons of support, preexisting applications to learn from, well maintained documentation, bindings, and libraries, and published books on .NET/C#/Mono.</p>
<p>At first, I viewed C# as merely a better version of Java and became a bit bored with the language about a year and a half ago. I started writing a lot of Haskell, and C# just didn&#8217;t seem fun enough to warrant coding in my spare time. After C# 3.0 came out, I fell in LOVE with the language &#8212; LINQ, lambdas, and type inference made it really easy to do the kind of higher-order programming I thoroughly enjoy. Microsoft Research employs a group of really brainy PL researchers like Eric Meijer and Simon-Peyton Jones, so a lot of functional features from languages like F# and Haskell are making their way into successive generations of C#. It really is a cutting-edge language in mainstream language clothing <img src='http://davidsiegel.org/wp-content/plugins/tango-smileys-extended/tango/smile.png' alt='Smile' title='Smile' class='tse-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael Nerode</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1463</link>
		<dc:creator>Nathanael Nerode</dc:creator>
		<pubDate>Mon, 06 Jul 2009 22:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1463</guid>
		<description>&quot;Interview stakeholders. Figure out why developers like me are using Mono; I love Mono and would be happy to tell you why.&quot;

I would like to know why, as a developer who is considering Mono but tends to prefer to stick to more established, long-tested platforms, for futureproofing.

(I really should get around to writing my &#039;version of make which actually works correcly for complex projects, like PROLOG does&#039;, though.  It&#039;s hilariously absurd that nobody has done this correctly in *any* of these postmodern development environments -- I guess nobody studies PROLOG any more)

Why?  Could you point us to some such explanations?</description>
		<content:encoded><![CDATA[<p>&#8220;Interview stakeholders. Figure out why developers like me are using Mono; I love Mono and would be happy to tell you why.&#8221;</p>
<p>I would like to know why, as a developer who is considering Mono but tends to prefer to stick to more established, long-tested platforms, for futureproofing.</p>
<p>(I really should get around to writing my &#8216;version of make which actually works correcly for complex projects, like PROLOG does&#8217;, though.  It&#8217;s hilariously absurd that nobody has done this correctly in *any* of these postmodern development environments &#8212; I guess nobody studies PROLOG any more)</p>
<p>Why?  Could you point us to some such explanations?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Alton</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1431</link>
		<dc:creator>Brett Alton</dc:creator>
		<pubDate>Mon, 06 Jul 2009 20:39:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1431</guid>
		<description>Hey David,

I think you might want to make a post (when you have time and your fingers stop bleeding from Paper Cuts) on why you like C#. I&#039;m about to learn C# for my CS degree here in Canada and it seems to be of significant debate to the FOSS community so I think many people, including myself would be interested in hearing what you have to say.

Also, I read that you worked for IdeaLab and now you&#039;re working for Canonical, but above you also said you did some Python programming for Google. Your work background sounds pretty extensive, mind making a post or a quick comment on it?

Best of luck to you at Canonical! Hope your dream of Banshee becoming the default audio player comes true too!</description>
		<content:encoded><![CDATA[<p>Hey David,</p>
<p>I think you might want to make a post (when you have time and your fingers stop bleeding from Paper Cuts) on why you like C#. I&#8217;m about to learn C# for my CS degree here in Canada and it seems to be of significant debate to the FOSS community so I think many people, including myself would be interested in hearing what you have to say.</p>
<p>Also, I read that you worked for IdeaLab and now you&#8217;re working for Canonical, but above you also said you did some Python programming for Google. Your work background sounds pretty extensive, mind making a post or a quick comment on it?</p>
<p>Best of luck to you at Canonical! Hope your dream of Banshee becoming the default audio player comes true too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mathew</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1424</link>
		<dc:creator>mathew</dc:creator>
		<pubDate>Thu, 02 Jul 2009 22:14:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1424</guid>
		<description>My suggestion:

Switch to KDE and Kubuntu.

If enough people are seen to be switching because of Mono, it will be dropped.</description>
		<content:encoded><![CDATA[<p>My suggestion:</p>
<p>Switch to KDE and Kubuntu.</p>
<p>If enough people are seen to be switching because of Mono, it will be dropped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1461</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Wed, 01 Jul 2009 03:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1461</guid>
		<description>Vala is a possible alternative to Mono. I like that it&#039;s a C#-like language with C-like performance.

But seriously FFS there is no point to removing Mono. It&#039;s a open source RAD development framework with good performance! It&#039;s not like Vala which is new, it&#039;s got a large base of professionals already versed in it&#039;s development practices. It&#039;s sheer existence encourages Linux development. It&#039;s a very good thing (tm).

IMO if we ignore Mono we hurt the Linux desktop.</description>
		<content:encoded><![CDATA[<p>Vala is a possible alternative to Mono. I like that it&#8217;s a C#-like language with C-like performance.</p>
<p>But seriously FFS there is no point to removing Mono. It&#8217;s a open source RAD development framework with good performance! It&#8217;s not like Vala which is new, it&#8217;s got a large base of professionals already versed in it&#8217;s development practices. It&#8217;s sheer existence encourages Linux development. It&#8217;s a very good thing &#8482;.</p>
<p>IMO if we ignore Mono we hurt the Linux desktop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christoph</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1460</link>
		<dc:creator>Christoph</dc:creator>
		<pubDate>Tue, 30 Jun 2009 13:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1460</guid>
		<description>That&#039;s such a great post. I like the fact that the mono community doesn&#039;t reply in the same aggressive childish way they is facing from the anti mono community. Keep up the good work!</description>
		<content:encoded><![CDATA[<p>That&#8217;s such a great post. I like the fact that the mono community doesn&#8217;t reply in the same aggressive childish way they is facing from the anti mono community. Keep up the good work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joe</title>
		<link>http://davidsiegel.org/five-steps-to-vanquish-mono/comment-page-2/#comment-1459</link>
		<dc:creator>joe</dc:creator>
		<pubDate>Tue, 30 Jun 2009 03:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.davebsd.com/?p=368#comment-1459</guid>
		<description>using mono is only furthering ms interests. Richard Stallman will be seen in the future to have been right. It will of course be too late by then. To bad for Linux. Thank God for KDE...</description>
		<content:encoded><![CDATA[<p>using mono is only furthering ms interests. Richard Stallman will be seen in the future to have been right. It will of course be too late by then. To bad for Linux. Thank God for KDE&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
