<?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: coherency vs. incrementalism</title>
	<atom:link href="http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/</link>
	<description>I love you.</description>
	<lastBuildDate>Wed, 25 Jan 2012 17:08:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: AndersH</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207701</link>
		<dc:creator>AndersH</dc:creator>
		<pubDate>Wed, 12 Aug 2009 05:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207701</guid>
		<description>&gt; There’s no subset of Javascript that is really efficient.

You sound confident. Your statement is of course easy to disprove. But that was why I also mentioned type annotations.</description>
		<content:encoded><![CDATA[<p>&gt; There’s no subset of Javascript that is really efficient.</p>
<p>You sound confident. Your statement is of course easy to disprove. But that was why I also mentioned type annotations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: modeless</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207656</link>
		<dc:creator>modeless</dc:creator>
		<pubDate>Tue, 11 Aug 2009 23:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207656</guid>
		<description>Yeah, I&#039;m really looking forward to WebGL; it should make the performance bottlenecks obvious and will hopefully suggest some simple solutions :-)</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;m really looking forward to WebGL; it should make the performance bottlenecks obvious and will hopefully suggest some simple solutions :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Blizzard</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207651</link>
		<dc:creator>Christopher Blizzard</dc:creator>
		<pubDate>Tue, 11 Aug 2009 23:20:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207651</guid>
		<description>Yeah, that&#039;s probably the case.  But we&#039;ll know more once we have more in-the-field testing.  It might be enough to add a data structure to support those kinds of things.  We&#039;ll learn and iterate based on what we hear, for sure.</description>
		<content:encoded><![CDATA[<p>Yeah, that&#8217;s probably the case.  But we&#8217;ll know more once we have more in-the-field testing.  It might be enough to add a data structure to support those kinds of things.  We&#8217;ll learn and iterate based on what we hear, for sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: modeless</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207650</link>
		<dc:creator>modeless</dc:creator>
		<pubDate>Tue, 11 Aug 2009 23:01:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207650</guid>
		<description>I did read that article and TraceMonkey is exceedingly cool; however going by the diagram there the overhead is still 3x worse than C or Java in the best case, and of course there are huge performance cliffs to fall off of everywhere.  

Processing isn&#039;t the only problem; storage may actually be the bigger issue.  As far as I know there&#039;s no way to efficiently store something like a vertex buffer with interleaved floats and bytes in Javascript.</description>
		<content:encoded><![CDATA[<p>I did read that article and TraceMonkey is exceedingly cool; however going by the diagram there the overhead is still 3x worse than C or Java in the best case, and of course there are huge performance cliffs to fall off of everywhere.  </p>
<p>Processing isn&#8217;t the only problem; storage may actually be the bigger issue.  As far as I know there&#8217;s no way to efficiently store something like a vertex buffer with interleaved floats and bytes in Javascript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Blizzard</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207648</link>
		<dc:creator>Christopher Blizzard</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207648</guid>
		<description>@Modeless For numbers that don&#039;t change types very much TraceMonkey does very well at processing them.  Please see this article:

http://hacks.mozilla.org/2009/07/tracemonkey-overview/

It talks about how we can actually make processing number types very fast.  (In fact, we do better than the other JS engines at this particular type of processing.)

Keep in mind that we&#039;ll be learning as we go here.  If we find a particular kind of operation that&#039;s too slow we can always add APIs for those kinds of things.  That&#039;s how the web has changed over the last couple of years - start simple, help libraries optimize as we go.</description>
		<content:encoded><![CDATA[<p>@Modeless For numbers that don&#8217;t change types very much TraceMonkey does very well at processing them.  Please see this article:</p>
<p><a href="http://hacks.mozilla.org/2009/07/tracemonkey-overview/" rel="nofollow">http://hacks.mozilla.org/2009/07/tracemonkey-overview/</a></p>
<p>It talks about how we can actually make processing number types very fast.  (In fact, we do better than the other JS engines at this particular type of processing.)</p>
<p>Keep in mind that we&#8217;ll be learning as we go here.  If we find a particular kind of operation that&#8217;s too slow we can always add APIs for those kinds of things.  That&#8217;s how the web has changed over the last couple of years &#8211; start simple, help libraries optimize as we go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: modeless</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207609</link>
		<dc:creator>modeless</dc:creator>
		<pubDate>Tue, 11 Aug 2009 18:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207609</guid>
		<description>There&#039;s no subset of Javascript that is really efficient.  The problem is that Javascript has only one numeric type which morphs from int to double on overflow (which requires constant overflow checking).  There&#039;s no way to allocate and/or efficiently process a large array of bytes, floats, int64s, or any numeric type of a specific size.  This is a problem for processing buffers containing vertices, pixels, audio samples, or similar data.

Perhaps all that is needed is a way to allocate arrays of specific numeric types in Javascript.</description>
		<content:encoded><![CDATA[<p>There&#8217;s no subset of Javascript that is really efficient.  The problem is that Javascript has only one numeric type which morphs from int to double on overflow (which requires constant overflow checking).  There&#8217;s no way to allocate and/or efficiently process a large array of bytes, floats, int64s, or any numeric type of a specific size.  This is a problem for processing buffers containing vertices, pixels, audio samples, or similar data.</p>
<p>Perhaps all that is needed is a way to allocate arrays of specific numeric types in Javascript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207581</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Tue, 11 Aug 2009 15:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207581</guid>
		<description>You can use jQuery and Mootools and Prototype to script a PHP page that uses MySQL and MS-SQL databases to retrieve information in XHTML, SVG, RDFa, and Microformats.
And yes, that would be messy.

When it comes down to it, the web is just about choice. If developers stick with a few different technologies, it&#039;s actually not messy at all.

I like the web technologies because it&#039;s all interpreted. Sure, the different engines will render things a bit differently from each-other, but I love that I can change things in the middle of a program. You just can&#039;t do that with Java or C or such.</description>
		<content:encoded><![CDATA[<p>You can use jQuery and Mootools and Prototype to script a PHP page that uses MySQL and MS-SQL databases to retrieve information in XHTML, SVG, RDFa, and Microformats.<br />
And yes, that would be messy.</p>
<p>When it comes down to it, the web is just about choice. If developers stick with a few different technologies, it&#8217;s actually not messy at all.</p>
<p>I like the web technologies because it&#8217;s all interpreted. Sure, the different engines will render things a bit differently from each-other, but I love that I can change things in the middle of a program. You just can&#8217;t do that with Java or C or such.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AndersH</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207580</link>
		<dc:creator>AndersH</dc:creator>
		<pubDate>Tue, 11 Aug 2009 15:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207580</guid>
		<description>Why would a &quot;language-agnostic VM&quot; be faster than a language-specific VM? I believe the way to go is, that if there are features of javascript that make it to hard to execute efficiently, an efficient subset should be found (assuming that one exist) and documented or perhaps enforced via a strict-option and optional type annotations could be added.

The open web might have started to gain some new features, but where are the polished showcases? There seems to tech-demos out there.</description>
		<content:encoded><![CDATA[<p>Why would a &#8220;language-agnostic VM&#8221; be faster than a language-specific VM? I believe the way to go is, that if there are features of javascript that make it to hard to execute efficiently, an efficient subset should be found (assuming that one exist) and documented or perhaps enforced via a strict-option and optional type annotations could be added.</p>
<p>The open web might have started to gain some new features, but where are the polished showcases? There seems to tech-demos out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dcbw</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207577</link>
		<dc:creator>dcbw</dc:creator>
		<pubDate>Tue, 11 Aug 2009 14:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207577</guid>
		<description>Development tools.  Where&#039;s the &quot;web IDE&quot; that other platforms like flash/silverlight/.net/cocoa have?  Most IDEs make the barrier-to-entry a ton lower and thus help attract new developers.  Yeah, some people don&#039;t mind having 10 different tools with 10 different interfaces to accopmlish their task, but huge swaths of developers only know an IDE, because IDEs fill a large part of the requirements.

So maybe if there was (already is?) something for Eclipse that just made JS + HTML + CSS + XMLRPC development a ton easier, we&#039;d be close.</description>
		<content:encoded><![CDATA[<p>Development tools.  Where&#8217;s the &#8220;web IDE&#8221; that other platforms like flash/silverlight/.net/cocoa have?  Most IDEs make the barrier-to-entry a ton lower and thus help attract new developers.  Yeah, some people don&#8217;t mind having 10 different tools with 10 different interfaces to accopmlish their task, but huge swaths of developers only know an IDE, because IDEs fill a large part of the requirements.</p>
<p>So maybe if there was (already is?) something for Eclipse that just made JS + HTML + CSS + XMLRPC development a ton easier, we&#8217;d be close.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: modeless</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/08/coherency-vs-incrementalism/comment-page-1/#comment-207517</link>
		<dc:creator>modeless</dc:creator>
		<pubDate>Tue, 11 Aug 2009 00:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1355#comment-207517</guid>
		<description>I&#039;m not too worried about the &quot;coherence&quot; or &quot;messiness&quot; of the platform.  My main concern is for Javascript as the only language.  New sandboxed APIs for graphics, audio, and video are great, and I&#039;m no Javascript hater but I&#039;m skeptical it can reach the performance we need.  I want to do cutting-edge 3D games, video encoding and editing, real-time audio effects, etc.  Javascript&#039;s type system makes it hard to do math on large arrays of numbers efficiently.  A language-agnostic VM might be better in the long term.

Or, for a different solution, perhaps we can expose OpenCL to Javascript in the same way we&#039;re doing OpenGL, and do all the heavy numeric lifting that way.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not too worried about the &#8220;coherence&#8221; or &#8220;messiness&#8221; of the platform.  My main concern is for Javascript as the only language.  New sandboxed APIs for graphics, audio, and video are great, and I&#8217;m no Javascript hater but I&#8217;m skeptical it can reach the performance we need.  I want to do cutting-edge 3D games, video encoding and editing, real-time audio effects, etc.  Javascript&#8217;s type system makes it hard to do math on large arrays of numbers efficiently.  A language-agnostic VM might be better in the long term.</p>
<p>Or, for a different solution, perhaps we can expose OpenCL to Javascript in the same way we&#8217;re doing OpenGL, and do all the heavy numeric lifting that way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

