<?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: The Non-Existent Linux Project</title>
	<atom:link href="http://piestar.net/2010/06/08/the-non-existent-linux-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/</link>
	<description>A pragmatic look at the state of FOSS</description>
	<lastBuildDate>Fri, 11 May 2012 02:40:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Door Pin Insert Kit By Omix &#124; Dorianclifton124&#039;s Blog</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8367</link>
		<dc:creator>Door Pin Insert Kit By Omix &#124; Dorianclifton124&#039;s Blog</dc:creator>
		<pubDate>Fri, 09 Jul 2010 21:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8367</guid>
		<description>[...] Door Pin Insert Kit By&#160;Omix  Posted on July 9, 2010 by dorianclifton124   The Non-Existent Linux Project &#124; Piestar [...]</description>
		<content:encoded><![CDATA[<p>[...] Door Pin Insert Kit By&nbsp;Omix  Posted on July 9, 2010 by dorianclifton124   The Non-Existent Linux Project | Piestar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Door Pin Insert Kit By Omix &#124; Efrainfortis289&#039;s Blog</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8362</link>
		<dc:creator>Door Pin Insert Kit By Omix &#124; Efrainfortis289&#039;s Blog</dc:creator>
		<pubDate>Fri, 09 Jul 2010 15:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8362</guid>
		<description>[...] Door Pin Insert Kit By&#160;Omix  Posted on July 9, 2010 by efrainfortis289   The Non-Existent Linux Project &#124; Piestar [...]</description>
		<content:encoded><![CDATA[<p>[...] Door Pin Insert Kit By&nbsp;Omix  Posted on July 9, 2010 by efrainfortis289   The Non-Existent Linux Project | Piestar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Door Pin Insert Kit By Omix &#124; Careybautista246&#039;s Blog</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8316</link>
		<dc:creator>Door Pin Insert Kit By Omix &#124; Careybautista246&#039;s Blog</dc:creator>
		<pubDate>Wed, 07 Jul 2010 19:00:27 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8316</guid>
		<description>[...] Door Pin Insert Kit By&#160;Omix  Posted on July 7, 2010 by careybautista246   The Non-Existent Linux Project &#124; Piestar [...]</description>
		<content:encoded><![CDATA[<p>[...] Door Pin Insert Kit By&nbsp;Omix  Posted on July 7, 2010 by careybautista246   The Non-Existent Linux Project | Piestar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Door Pin Insert Kit By Omix &#124; My Super Sport Blog</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8284</link>
		<dc:creator>Door Pin Insert Kit By Omix &#124; My Super Sport Blog</dc:creator>
		<pubDate>Tue, 06 Jul 2010 22:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8284</guid>
		<description>[...] Door Pin Insert Kit By&#160;Omix  Posted on July 6, 2010 by merledua239   The Non-Existent Linux Project &#124; Piestar [...]</description>
		<content:encoded><![CDATA[<p>[...] Door Pin Insert Kit By&nbsp;Omix  Posted on July 6, 2010 by merledua239   The Non-Existent Linux Project | Piestar [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apostate</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8147</link>
		<dc:creator>Apostate</dc:creator>
		<pubDate>Thu, 01 Jul 2010 19:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8147</guid>
		<description>&quot;Mission: Create a usable Desktop OS – just to show the Linux fanboys what they should have done. Avoid GPL software wherever possible. Make it marketable.&quot;

So we&#039;ll use...what?

&quot;As a base we need a kernel etc. – one of the BSDs should do.&quot;

Because those kernels are more....something than Linux. Or less something else. Less compatible, and popular for sure. But hey, if the BSD license is so rad-tastic it will liberate us from the evils of the Linux Kernel with all its...Linuxy stuff, then ok.

&quot;(Include OSS for audio.)&quot;

Because it&#039;s old and sucks, and will really showcase the audio capabilities of our hypothetical non-Linux Eagle-BSD...the ultimate desktop...WATCH OUT APPLE! I can&#039;t wait to see who starts mixing records on Logic 8 for Eagle-BSD featuring the OSS audio architecture: A quantum Leap forward in sound sub-systems. Take that, Linux! We&#039;ll have OSS!

&quot; We need an application framework, which should be .NET because it...&quot;

...Blows, has memory leaks, couldn&#039;t even be used as a core language for Windows, is only implemented properly *on* Windows, requires a VM, reflects the biases of the posters here, and may infringe on Microsoft Intellectual Property rights if you implement it in Mono-- oh yes,  and will result in slow-as-fuck apps like all the ones on Linux you hate. Not even &quot;Linux Zealots&quot; like Mono much, but you&#039;ll show them!


 &quot;exists, isn’t bad (AFAIK it’s even pretty good) and there are existing applications.&quot; 

For Windows. Or did you mean the GPL apps like F-Spot (ghey) and Banshee?

&quot;X11 doesn’t cut it, so create a graphic “layer” to sit on the kernel and provide the necessary services for the .NET framework. &quot;

Yeah, only a Linux nerd would use X11. Let&#039;s conjure up a &quot;layer&quot; thingie and provide...WinForms? Or DirectX controls? Good luck licensing that. 


&quot;If QT provides any help with this, license it and use it.&quot;

Ummm....with yer thingie layer-dealie? Or?? Is that tied right into the Warp Engines?

Fucking amazing. I think the blog owner cited the Dunning-Kruger effect in another post. I hope his readers Googled that. I just thank the Usability Gods that you guys are here to save the Heathens from the fatally-flawed Linux. Whew.</description>
		<content:encoded><![CDATA[<p>&#8220;Mission: Create a usable Desktop OS – just to show the Linux fanboys what they should have done. Avoid GPL software wherever possible. Make it marketable.&#8221;</p>
<p>So we&#8217;ll use&#8230;what?</p>
<p>&#8220;As a base we need a kernel etc. – one of the BSDs should do.&#8221;</p>
<p>Because those kernels are more&#8230;.something than Linux. Or less something else. Less compatible, and popular for sure. But hey, if the BSD license is so rad-tastic it will liberate us from the evils of the Linux Kernel with all its&#8230;Linuxy stuff, then ok.</p>
<p>&#8220;(Include OSS for audio.)&#8221;</p>
<p>Because it&#8217;s old and sucks, and will really showcase the audio capabilities of our hypothetical non-Linux Eagle-BSD&#8230;the ultimate desktop&#8230;WATCH OUT APPLE! I can&#8217;t wait to see who starts mixing records on Logic 8 for Eagle-BSD featuring the OSS audio architecture: A quantum Leap forward in sound sub-systems. Take that, Linux! We&#8217;ll have OSS!</p>
<p>&#8221; We need an application framework, which should be .NET because it&#8230;&#8221;</p>
<p>&#8230;Blows, has memory leaks, couldn&#8217;t even be used as a core language for Windows, is only implemented properly *on* Windows, requires a VM, reflects the biases of the posters here, and may infringe on Microsoft Intellectual Property rights if you implement it in Mono&#8211; oh yes,  and will result in slow-as-fuck apps like all the ones on Linux you hate. Not even &#8220;Linux Zealots&#8221; like Mono much, but you&#8217;ll show them!</p>
<p> &#8220;exists, isn’t bad (AFAIK it’s even pretty good) and there are existing applications.&#8221; </p>
<p>For Windows. Or did you mean the GPL apps like F-Spot (ghey) and Banshee?</p>
<p>&#8220;X11 doesn’t cut it, so create a graphic “layer” to sit on the kernel and provide the necessary services for the .NET framework. &#8221;</p>
<p>Yeah, only a Linux nerd would use X11. Let&#8217;s conjure up a &#8220;layer&#8221; thingie and provide&#8230;WinForms? Or DirectX controls? Good luck licensing that. </p>
<p>&#8220;If QT provides any help with this, license it and use it.&#8221;</p>
<p>Ummm&#8230;.with yer thingie layer-dealie? Or?? Is that tied right into the Warp Engines?</p>
<p>Fucking amazing. I think the blog owner cited the Dunning-Kruger effect in another post. I hope his readers Googled that. I just thank the Usability Gods that you guys are here to save the Heathens from the fatally-flawed Linux. Whew.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apostate</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-8146</link>
		<dc:creator>Apostate</dc:creator>
		<pubDate>Thu, 01 Jul 2010 19:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-8146</guid>
		<description>&quot;
freehunter said: 2010.06.09 03:14

I completely agree with this post. Linux is completely unusable. I use it every day &quot;

Yeah, zealotry is a problem. Quite a few on this blog. Wow. Talk about cognitive dissonance.</description>
		<content:encoded><![CDATA[<p>&#8221;<br />
freehunter said: 2010.06.09 03:14</p>
<p>I completely agree with this post. Linux is completely unusable. I use it every day &#8221;</p>
<p>Yeah, zealotry is a problem. Quite a few on this blog. Wow. Talk about cognitive dissonance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr Loser</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-7834</link>
		<dc:creator>Dr Loser</dc:creator>
		<pubDate>Wed, 16 Jun 2010 12:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-7834</guid>
		<description>The sliding rule interface is a simple version of what I was muddle-headedly aiming at: I&#039;m trying to get away from the browser paradigm, which essentially does this with absolutely no intelligence attached.  I think what I&#039;m suggesting is a sort of &quot;event network,&quot; whereby the UI captures what it can -- launching apps, task switching, button-pressing, etc -- and tries to make sense of it for a given session or workflow.  This is more akin to what the better automated test tools do.

Project-oriented (asset-oriented) storage in some form would be great.  There&#039;s a reason IDEs exist ... in fact, representing the entire file system in an IDE (with pluggable extensions, yet) would be a heck of a better paradigm that this stupid folder thing.

Of course, third-party installers (ie the whole of the rest of the world) would still insist on the old paradigm, so you&#039;d still need a mirror filesystem that looks like, sigh, the Unix one.  Well, Linux still needs a CLI.  I guess you need a certain degree of backward compatibility.</description>
		<content:encoded><![CDATA[<p>The sliding rule interface is a simple version of what I was muddle-headedly aiming at: I&#8217;m trying to get away from the browser paradigm, which essentially does this with absolutely no intelligence attached.  I think what I&#8217;m suggesting is a sort of &#8220;event network,&#8221; whereby the UI captures what it can &#8212; launching apps, task switching, button-pressing, etc &#8212; and tries to make sense of it for a given session or workflow.  This is more akin to what the better automated test tools do.</p>
<p>Project-oriented (asset-oriented) storage in some form would be great.  There&#8217;s a reason IDEs exist &#8230; in fact, representing the entire file system in an IDE (with pluggable extensions, yet) would be a heck of a better paradigm that this stupid folder thing.</p>
<p>Of course, third-party installers (ie the whole of the rest of the world) would still insist on the old paradigm, so you&#8217;d still need a mirror filesystem that looks like, sigh, the Unix one.  Well, Linux still needs a CLI.  I guess you need a certain degree of backward compatibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TM Repository</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-7824</link>
		<dc:creator>TM Repository</dc:creator>
		<pubDate>Tue, 15 Jun 2010 23:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-7824</guid>
		<description>I&#039;d propose some sort of sliding rule interface that brings your most-used applications (assuming we even go the standard application route), tasks and documents to the forefront.  This gives a logical way of finding lesser used functions; start near the back of the stack/timeline/ruler/etc.  Bear in mind, this is a concept, not a fleshed out model.

Secondly, project-oriented storage.  It&#039;s a real pain having to try and force a folder hierarchy to mimic a project.  I propose the idea of project-oriented storage with projects and assets rather than folders and files.  The benefits to this become clearer when you take into account the ability to reference one asset into other assets elsewhere within a project.  Likewise, all tasks/applications that contribute to a project become linked to it so that there is a complete history of changes made and those changes can be baked, altered, or rolled back.

Think of it this way, you don&#039;t have a Word document, you have a text asset that needs to be combined with a logo asset made of vector art that can then be consumed by a printing task.  This way, tasks can consume and remodel a project as it deems fit to complete its task.</description>
		<content:encoded><![CDATA[<p>I&#8217;d propose some sort of sliding rule interface that brings your most-used applications (assuming we even go the standard application route), tasks and documents to the forefront.  This gives a logical way of finding lesser used functions; start near the back of the stack/timeline/ruler/etc.  Bear in mind, this is a concept, not a fleshed out model.</p>
<p>Secondly, project-oriented storage.  It&#8217;s a real pain having to try and force a folder hierarchy to mimic a project.  I propose the idea of project-oriented storage with projects and assets rather than folders and files.  The benefits to this become clearer when you take into account the ability to reference one asset into other assets elsewhere within a project.  Likewise, all tasks/applications that contribute to a project become linked to it so that there is a complete history of changes made and those changes can be baked, altered, or rolled back.</p>
<p>Think of it this way, you don&#8217;t have a Word document, you have a text asset that needs to be combined with a logo asset made of vector art that can then be consumed by a printing task.  This way, tasks can consume and remodel a project as it deems fit to complete its task.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr Loser</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-7820</link>
		<dc:creator>Dr Loser</dc:creator>
		<pubDate>Tue, 15 Jun 2010 14:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-7820</guid>
		<description>That thing about RAD, btw; I did qualify it with &quot;YMMV.&quot;  Like &quot;agile,&quot; it often falls into the category of a Silver Bullet.  Where possible, I try to avoid jobs that are based around a silver bullet.  It&#039;s increasingly impossible.

@Carsten: Pretty much everything Joel has written about UI development would apply, although I have a sneaking suspicion that Kerberos was there before him and has thought more carefully about it afterwards.  It&#039;s a useful resource for ignoramuses like me, however.

*Obviously* you&#039;d have to include aesthetics, however difficult that criterion might be to judge.  Where would anything marketed by Jobs be without aesthetics?  There&#039;s at least one basic issue to resolve asap, which is to choose between pixel-based font-rendering and aesthetics-based font-rendering (Joel again).

I&#039;m a programmer, not a designer, so a couple of other things spring to mind.

You also have to consider Unity. (I can&#039;t think of a better word to describe what I mean.) An obvious counter-example to Unity is the long-standing X issue with cut &amp; paste.  Who knows when it will work and when it won&#039;t? It&#039;s not unreasonable to start with the Linux Desktop as a series of inaccurately linked design decisions and then consciously strive to avoid all of them. (From an Apple point of view, Unity seems to be embedded by virtue of Cocoa, so I&#039;d still want a mandatory scripting framework for absolutely everything.)

One more thing which is *not* part of any current desktop, so far as I can see.  There&#039;s enough computing power out there, these days, to allow for an UberPaperclip to offer sensible AI-style help.  Maybe current HMI work is going in this direction, although I have no information on the subject.  It&#039;d be really nice if one could utilise anti-spam techniques in reverse and actually &quot;guess&quot; what the user is thinking -- related files or apps, maybe relevant personal contacts or music/visuals, whatever.

It&#039;s not strictly part of the remit, but it would be a fabulous addition.  No idea how you&#039;d make it unobtrusive, though...</description>
		<content:encoded><![CDATA[<p>That thing about RAD, btw; I did qualify it with &#8220;YMMV.&#8221;  Like &#8220;agile,&#8221; it often falls into the category of a Silver Bullet.  Where possible, I try to avoid jobs that are based around a silver bullet.  It&#8217;s increasingly impossible.</p>
<p>@Carsten: Pretty much everything Joel has written about UI development would apply, although I have a sneaking suspicion that Kerberos was there before him and has thought more carefully about it afterwards.  It&#8217;s a useful resource for ignoramuses like me, however.</p>
<p>*Obviously* you&#8217;d have to include aesthetics, however difficult that criterion might be to judge.  Where would anything marketed by Jobs be without aesthetics?  There&#8217;s at least one basic issue to resolve asap, which is to choose between pixel-based font-rendering and aesthetics-based font-rendering (Joel again).</p>
<p>I&#8217;m a programmer, not a designer, so a couple of other things spring to mind.</p>
<p>You also have to consider Unity. (I can&#8217;t think of a better word to describe what I mean.) An obvious counter-example to Unity is the long-standing X issue with cut &amp; paste.  Who knows when it will work and when it won&#8217;t? It&#8217;s not unreasonable to start with the Linux Desktop as a series of inaccurately linked design decisions and then consciously strive to avoid all of them. (From an Apple point of view, Unity seems to be embedded by virtue of Cocoa, so I&#8217;d still want a mandatory scripting framework for absolutely everything.)</p>
<p>One more thing which is *not* part of any current desktop, so far as I can see.  There&#8217;s enough computing power out there, these days, to allow for an UberPaperclip to offer sensible AI-style help.  Maybe current HMI work is going in this direction, although I have no information on the subject.  It&#8217;d be really nice if one could utilise anti-spam techniques in reverse and actually &#8220;guess&#8221; what the user is thinking &#8212; related files or apps, maybe relevant personal contacts or music/visuals, whatever.</p>
<p>It&#8217;s not strictly part of the remit, but it would be a fabulous addition.  No idea how you&#8217;d make it unobtrusive, though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carsten Hardt</title>
		<link>http://piestar.net/2010/06/08/the-non-existent-linux-project/#comment-7819</link>
		<dc:creator>Carsten Hardt</dc:creator>
		<pubDate>Tue, 15 Jun 2010 14:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://piestar.net/?p=485#comment-7819</guid>
		<description>@TMR: &quot;What criteria do we use to evaluate an interface?&quot;
Good question, and I mostly agree with your criteria (I&#039;m not so sure about aesthetics as such, but contrast is definitely an issue.) Do I dare suggest as another criteria &quot;Controlling Your Environment Makes You Happy&quot; ?
http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html</description>
		<content:encoded><![CDATA[<p>@TMR: &#8220;What criteria do we use to evaluate an interface?&#8221;<br />
Good question, and I mostly agree with your criteria (I&#8217;m not so sure about aesthetics as such, but contrast is definitely an issue.) Do I dare suggest as another criteria &#8220;Controlling Your Environment Makes You Happy&#8221; ?<br />
<a href="http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html" rel="nofollow">http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

