<?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 for Code diary</title>
	<atom:link href="http://piacentini.blog.br/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://piacentini.blog.br</link>
	<description>a free software blog</description>
	<lastBuildDate>Sun, 13 Feb 2011 15:54:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Elop is after me by Mauricio Piacentini</title>
		<link>http://piacentini.blog.br/2011/02/elop-is-after-me/#comment-345</link>
		<dc:creator>Mauricio Piacentini</dc:creator>
		<pubDate>Sun, 13 Feb 2011 15:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://piacentini.blog.br/?p=403#comment-345</guid>
		<description><![CDATA[I respect your opinion, just not agree with the need to keep silent. How about the thousands of people that submitted applications to the OVI store, or invested in creating them? And the people that invested heavily in learning Qt/QML and have prototypes that were just waiting the first Nokia/MeeGo phone, which was assured no more than 2-3 months ago at Dublin? Are these not community issues?

The *possibility* of a community fork is one of the things that might make Nokia&#039;s management still do the right thing (keep investment and the QtSW division people jobs). And while this possibility is something you know about, there are definitively Qt developers that are panicking right now because they do not know that, no matter what Nokia decides to do, there is a reassured escape route, thanks to the GPL and FreeQt foundation.

So the message, for me, should be: &quot;We are behind Qt, it will thrive no matter what happens. It will continue either internally at Nokia or via a community-supported version&quot;. This is not FUD, is reassurance and commitment to your toolkit. If anything, it avoids panic. Intel, with its thousands of managers and internal policies, was quick to react, in a very direct press release, KDE imo should do the same in order to calm their users so they know that there are options and we are not automatically depending on MS. ]]></description>
		<content:encoded><![CDATA[<p>I respect your opinion, just not agree with the need to keep silent. How about the thousands of people that submitted applications to the OVI store, or invested in creating them? And the people that invested heavily in learning Qt/QML and have prototypes that were just waiting the first Nokia/MeeGo phone, which was assured no more than 2-3 months ago at Dublin? Are these not community issues?</p>
<p>The *possibility* of a community fork is one of the things that might make Nokia&#8217;s management still do the right thing (keep investment and the QtSW division people jobs). And while this possibility is something you know about, there are definitively Qt developers that are panicking right now because they do not know that, no matter what Nokia decides to do, there is a reassured escape route, thanks to the GPL and FreeQt foundation.</p>
<p>So the message, for me, should be: &#8220;We are behind Qt, it will thrive no matter what happens. It will continue either internally at Nokia or via a community-supported version&#8221;. This is not FUD, is reassurance and commitment to your toolkit. If anything, it avoids panic. Intel, with its thousands of managers and internal policies, was quick to react, in a very direct press release, KDE imo should do the same in order to calm their users so they know that there are options and we are not automatically depending on MS. </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Elop is after me by User</title>
		<link>http://piacentini.blog.br/2011/02/elop-is-after-me/#comment-344</link>
		<dc:creator>User</dc:creator>
		<pubDate>Sun, 13 Feb 2011 15:51:55 +0000</pubDate>
		<guid isPermaLink="false">http://piacentini.blog.br/?p=403#comment-344</guid>
		<description><![CDATA[&gt; Bad decision. By forking now, you’ll make things worse.

How ?

Think about how worse will be if the community doesn&#039;t fork it. Everyone is pretty aware how far M$ is willing to go. If they can do a hostile take over of Yahoo / Nokia - Qt ain&#039;t too much for them. Think about this.]]></description>
		<content:encoded><![CDATA[<p>&gt; Bad decision. By forking now, you’ll make things worse.</p>
<p>How ?</p>
<p>Think about how worse will be if the community doesn&#8217;t fork it. Everyone is pretty aware how far M$ is willing to go. If they can do a hostile take over of Yahoo / Nokia &#8211; Qt ain&#8217;t too much for them. Think about this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Elop is after me by Marcus</title>
		<link>http://piacentini.blog.br/2011/02/elop-is-after-me/#comment-343</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Sun, 13 Feb 2011 15:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://piacentini.blog.br/?p=403#comment-343</guid>
		<description><![CDATA[I can only second Aaron. Reading this kind of FUD as of now feels like an unreflected, premature reaction screamed out during a contemplative moment of silence.

Have you guys ever spent a single thought on the social side? Like all the bonds that have been created between the employees of Nokia (among them the Trolls), KDE, and whatnot people, held together by the Qt framework? And you are asking for a fork? That, really, makes me want to scream.]]></description>
		<content:encoded><![CDATA[<p>I can only second Aaron. Reading this kind of FUD as of now feels like an unreflected, premature reaction screamed out during a contemplative moment of silence.</p>
<p>Have you guys ever spent a single thought on the social side? Like all the bonds that have been created between the employees of Nokia (among them the Trolls), KDE, and whatnot people, held together by the Qt framework? And you are asking for a fork? That, really, makes me want to scream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Elop is after me by Brian Duffy</title>
		<link>http://piacentini.blog.br/2011/02/elop-is-after-me/#comment-341</link>
		<dc:creator>Brian Duffy</dc:creator>
		<pubDate>Sun, 13 Feb 2011 15:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://piacentini.blog.br/?p=403#comment-341</guid>
		<description><![CDATA[This is the discussion I have been looking for! Ever since the rumors of a Microsoft deal I have been wondering what would happen to Qt. Mauricio&#039;s experience is indicative of the situation I fear most. I mentioned on the Nokia forums that my greatest fear is that Nokia will keep just enough of a hold on Qt to let it stagnate. With a community as strong and determined as Qt has, I don&#039;t think they will ultimately be successful. But as Mauricio says, the community would be wise not to become complacent and let Nokia dictate Qt&#039;s direction for too long. Even before the announcement, I was experiencing frustration with Qt&#039;s focus on mobile platforms to the detriment of the general toolkit. I was trying to be patient because I felt like some of the new development would (and I hope ultimately will) strengthen the overall product. I really like what the trolls are doing with QML for instance. 

I think it is definitely time to move on from Nokia, thank God it is up to the community and not Nokia to make that decision. Wasting time welcomes developer apathy. For instance, I have been waiting for quite a while for the Qt team to settle their direction on video playback api&#039;s. While they worked on the issue, the future of the platform&#039;s video playback was incoveniently bundled with their mobile strategy. That is how I found this blog to begin with and I thank Mauricio for his contributions to QtGstreamer. 

I think we can only expect a frustratingly slow and insufficient upkeep of Qt under Nokia, so eventually (hopefully sooner than later) it will find a new home. This new home will of course have its own agenda for the upkeep and usage of the framework. Certainly, KDE has a huge interest in Qt. I personally do not use KDE. I wonder if they will have an agenda that works well for Qt development outside of the KDE environment. Will they be interested in QML? Why has there been a problem between trolls and KDE with submitting patches? I guess I am hoping that Qt does not just become a tool *fucused* on building applications for KDE. 

Thanks to Mauricio for providing a concrete and relevant example of the danger that is facing Qt in the coming year.

Brian Duffy]]></description>
		<content:encoded><![CDATA[<p>This is the discussion I have been looking for! Ever since the rumors of a Microsoft deal I have been wondering what would happen to Qt. Mauricio&#8217;s experience is indicative of the situation I fear most. I mentioned on the Nokia forums that my greatest fear is that Nokia will keep just enough of a hold on Qt to let it stagnate. With a community as strong and determined as Qt has, I don&#8217;t think they will ultimately be successful. But as Mauricio says, the community would be wise not to become complacent and let Nokia dictate Qt&#8217;s direction for too long. Even before the announcement, I was experiencing frustration with Qt&#8217;s focus on mobile platforms to the detriment of the general toolkit. I was trying to be patient because I felt like some of the new development would (and I hope ultimately will) strengthen the overall product. I really like what the trolls are doing with QML for instance. </p>
<p>I think it is definitely time to move on from Nokia, thank God it is up to the community and not Nokia to make that decision. Wasting time welcomes developer apathy. For instance, I have been waiting for quite a while for the Qt team to settle their direction on video playback api&#8217;s. While they worked on the issue, the future of the platform&#8217;s video playback was incoveniently bundled with their mobile strategy. That is how I found this blog to begin with and I thank Mauricio for his contributions to QtGstreamer. </p>
<p>I think we can only expect a frustratingly slow and insufficient upkeep of Qt under Nokia, so eventually (hopefully sooner than later) it will find a new home. This new home will of course have its own agenda for the upkeep and usage of the framework. Certainly, KDE has a huge interest in Qt. I personally do not use KDE. I wonder if they will have an agenda that works well for Qt development outside of the KDE environment. Will they be interested in QML? Why has there been a problem between trolls and KDE with submitting patches? I guess I am hoping that Qt does not just become a tool *fucused* on building applications for KDE. </p>
<p>Thanks to Mauricio for providing a concrete and relevant example of the danger that is facing Qt in the coming year.</p>
<p>Brian Duffy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Elop is after me by Luciano Moreira Camilo e Silva</title>
		<link>http://piacentini.blog.br/2011/02/elop-is-after-me/#comment-340</link>
		<dc:creator>Luciano Moreira Camilo e Silva</dc:creator>
		<pubDate>Sun, 13 Feb 2011 13:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://piacentini.blog.br/?p=403#comment-340</guid>
		<description><![CDATA[I just think about Intel. Other chip maker could get money with it, cause it can provide a agnostic tool to develop app to their processor. Hope it happen. Shame on you nokia!

PS.: I like microsoft as i like nokia and google, facebook and apple. I just don&#039;t like the partnership killing a visionary tool.]]></description>
		<content:encoded><![CDATA[<p>I just think about Intel. Other chip maker could get money with it, cause it can provide a agnostic tool to develop app to their processor. Hope it happen. Shame on you nokia!</p>
<p>PS.: I like microsoft as i like nokia and google, facebook and apple. I just don&#8217;t like the partnership killing a visionary tool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
