<?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"
	>
<channel>
	<title>Comments on: Restarting Innovation</title>
	<atom:link href="http://mjtsai.com/blog/2007/07/06/restarting-innovation/feed/" rel="self" type="application/rss+xml" />
	<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/</link>
	<description></description>
	<pubDate>Sun, 23 Nov 2008 10:37:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-106140</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 08 Jul 2007 16:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-106140</guid>
		<description>David Phillip Oster: That it's open source is yet another way that WebKit is an exception.</description>
		<content:encoded><![CDATA[<p>David Phillip Oster: That it's open source is yet another way that WebKit is an exception.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Phillip Oster</title>
		<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-106126</link>
		<dc:creator>David Phillip Oster</dc:creator>
		<pubDate>Sun, 08 Jul 2007 16:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-106126</guid>
		<description>I'm commenting on: "To build a really innovative application you may have to start from scratch, and then you’ll wish that the framework didn’t exist."

There is a huge difference between Webkit, and other frameworks from Apple, for example, NSTextView: Webkit is open source. You can get it from http://webkit.org .

So, your argument used to be true, until Webkit.

If you want to write a word processor with additional features, you have to throw away the additional 70% that NSTextView provides and start from zero, doing a huge amount of work just to get up to the level that NSTextView provides. If you want to write something that overlaps with Webkit, you can start with the source and build your app.

As a programmer, I say: yes please, Apple, give us more frameworks, with source code, and we'll give the people more apps.</description>
		<content:encoded><![CDATA[<p>I'm commenting on: "To build a really innovative application you may have to start from scratch, and then you’ll wish that the framework didn’t exist."</p>
<p>There is a huge difference between Webkit, and other frameworks from Apple, for example, NSTextView: Webkit is open source. You can get it from <a href="http://webkit.org" rel="nofollow">http://webkit.org</a> .</p>
<p>So, your argument used to be true, until Webkit.</p>
<p>If you want to write a word processor with additional features, you have to throw away the additional 70% that NSTextView provides and start from zero, doing a huge amount of work just to get up to the level that NSTextView provides. If you want to write something that overlaps with Webkit, you can start with the source and build your app.</p>
<p>As a programmer, I say: yes please, Apple, give us more frameworks, with source code, and we'll give the people more apps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105617</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 07 Jul 2007 14:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105617</guid>
		<description>JulesLt: I agree that data formats are important, but documenting them doesn't solve all problems. iPhoto has changed its library format several times, for example. I'd rather see a plug-in interface and an API to access the contents of the library. Apple did &lt;a href="http://developer.apple.com/appleapplications/keynote-apxl.html" rel="nofollow"&gt;document&lt;/a&gt; the &lt;a href="http://developer.apple.com/technotes/tn2002/tn2067.html" rel="nofollow"&gt;Keynote 1.x schema&lt;/a&gt;, but now that technote is marked as a legacy document. Word's XML format is documented, but it's so complex as to be inaccessible to most developers. I think it would be great if other applications could access data from Pages. Its "working format" is more interesting than the output format if you're trying to automate anything.</description>
		<content:encoded><![CDATA[<p>JulesLt: I agree that data formats are important, but documenting them doesn't solve all problems. iPhoto has changed its library format several times, for example. I'd rather see a plug-in interface and an API to access the contents of the library. Apple did <a href="http://developer.apple.com/appleapplications/keynote-apxl.html" rel="nofollow">document</a> the <a href="http://developer.apple.com/technotes/tn2002/tn2067.html" rel="nofollow">Keynote 1.x schema</a>, but now that technote is marked as a legacy document. Word's XML format is documented, but it's so complex as to be inaccessible to most developers. I think it would be great if other applications could access data from Pages. Its "working format" is more interesting than the output format if you're trying to automate anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JulesLt</title>
		<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105603</link>
		<dc:creator>JulesLt</dc:creator>
		<pubDate>Sat, 07 Jul 2007 14:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105603</guid>
		<description>All I think we really need is more and more application data to be held in databases, and some documented schemas. 

This is based on the observation that people used to think they wanted software compatibility - 'why can't I run program X on machine B'? Over time they've realised what they actually wanted data compatibility, and gradually standard formats emerged.

But there's still some data stuck in application specific silos - occasionally - as with Pages, iMovie, iDVD, Photoshop, that makes sense as they're 'working' formats where you 'publish' to another.</description>
		<content:encoded><![CDATA[<p>All I think we really need is more and more application data to be held in databases, and some documented schemas. </p>
<p>This is based on the observation that people used to think they wanted software compatibility - 'why can't I run program X on machine B'? Over time they've realised what they actually wanted data compatibility, and gradually standard formats emerged.</p>
<p>But there's still some data stuck in application specific silos - occasionally - as with Pages, iMovie, iDVD, Photoshop, that makes sense as they're 'working' formats where you 'publish' to another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105568</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Sat, 07 Jul 2007 12:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://mjtsai.com/blog/2007/07/06/restarting-innovation/#comment-105568</guid>
		<description>OmniWeb is based on a modified version of WebKit though. So it would probably work out well if the new frameworks were also open source, so that they could be modified to add the final 30 %.</description>
		<content:encoded><![CDATA[<p>OmniWeb is based on a modified version of WebKit though. So it would probably work out well if the new frameworks were also open source, so that they could be modified to add the final 30 %.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
