<?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: Why OpenGL 3.0 is Important</title>
	<atom:link href="http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/</link>
	<description>The informal yet informational sub-site</description>
	<lastBuildDate>Thu, 11 Mar 2010 04:55:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: OpenGL 3.0: Well, that explains it. &#124; Scriptionary Blog</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-441</link>
		<dc:creator>OpenGL 3.0: Well, that explains it. &#124; Scriptionary Blog</dc:creator>
		<pubDate>Fri, 22 Aug 2008 19:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-441</guid>
		<description>[...] a little history (May, 2008): In may I wrote a blog entry about the then upcoming OpenGL 3.0 based on information released by the Khronos ARB. The entry was [...]</description>
		<content:encoded><![CDATA[<p>[...] a little history (May, 2008): In may I wrote a blog entry about the then upcoming OpenGL 3.0 based on information released by the Khronos ARB. The entry was [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neonlabs &#187; Blog Archive &#187; OpenGL 3.0 Spec Released Today</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-421</link>
		<dc:creator>Neonlabs &#187; Blog Archive &#187; OpenGL 3.0 Spec Released Today</dc:creator>
		<pubDate>Thu, 21 Aug 2008 05:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-421</guid>
		<description>[...] and it was a complete disappointment (worse than version 2.0). Not even one feature that was promised nearly two years ago is in the spec for version 3.0. The Khronos Group has failed to provide a [...]</description>
		<content:encoded><![CDATA[<p>[...] and it was a complete disappointment (worse than version 2.0). Not even one feature that was promised nearly two years ago is in the spec for version 3.0. The Khronos Group has failed to provide a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenGL 3.0 uccide OpenGL e le speranze degli utenti Mac/Linux &#171; L&#8217;importante è avere un titolo</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-396</link>
		<dc:creator>OpenGL 3.0 uccide OpenGL e le speranze degli utenti Mac/Linux &#171; L&#8217;importante è avere un titolo</dc:creator>
		<pubDate>Sun, 17 Aug 2008 20:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-396</guid>
		<description>[...] aveva promesso, ad esempio, un&#8217;API orientata agli oggetti, seppur ancora basata su C. Un rifacimento quasi [...]</description>
		<content:encoded><![CDATA[<p>[...] aveva promesso, ad esempio, un&#8217;API orientata agli oggetti, seppur ancora basata su C. Un rifacimento quasi [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Culture News &#187; Blog Archive &#187; OpenGL 3.0 Released</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-372</link>
		<dc:creator>Free Culture News &#187; Blog Archive &#187; OpenGL 3.0 Released</dc:creator>
		<pubDate>Thu, 14 Aug 2008 14:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-372</guid>
		<description>[...] Scriptionary [...]</description>
		<content:encoded><![CDATA[<p>[...] Scriptionary [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenGL 3.0 publicat de Khronos Group &#171; Fly on the Windscreen</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-369</link>
		<dc:creator>OpenGL 3.0 publicat de Khronos Group &#171; Fly on the Windscreen</dc:creator>
		<pubDate>Wed, 13 Aug 2008 07:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-369</guid>
		<description>[...] multe despre de ce e important OpenGL 3.0 pe Scriptionary.  Publicat [...]</description>
		<content:encoded><![CDATA[<p>[...] multe despre de ce e important OpenGL 3.0 pe Scriptionary.  Publicat [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: martin b.r. &#187; Blog Archive &#187; OstionGL 3.0</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-368</link>
		<dc:creator>martin b.r. &#187; Blog Archive &#187; OstionGL 3.0</dc:creator>
		<pubDate>Tue, 12 Aug 2008 13:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-368</guid>
		<description>[...] las esperadas espeficicaciones de OpenGL 3. Nada de lo prometido, adios a la principal novedad, los objects y a la reorganizacion general. En muchos foros ya felicitan a Microsoft por ganar la guerra de las [...]</description>
		<content:encoded><![CDATA[<p>[...] las esperadas espeficicaciones de OpenGL 3. Nada de lo prometido, adios a la principal novedad, los objects y a la reorganizacion general. En muchos foros ya felicitan a Microsoft por ganar la guerra de las [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenGL 3.0 - 1 hour after &#124; Scriptionary Blog</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-366</link>
		<dc:creator>OpenGL 3.0 - 1 hour after &#124; Scriptionary Blog</dc:creator>
		<pubDate>Mon, 11 Aug 2008 14:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-366</guid>
		<description>[...] reading the spec and looking desperately for the promised object model, I felt quite like a douche bag taking the newsletters seriously and writing about them so [...]</description>
		<content:encoded><![CDATA[<p>[...] reading the spec and looking desperately for the promised object model, I felt quite like a douche bag taking the newsletters seriously and writing about them so [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ¿Para cuando OpenGL 3? &#171; culleredo</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-72</link>
		<dc:creator>¿Para cuando OpenGL 3? &#171; culleredo</dc:creator>
		<pubDate>Sun, 25 May 2008 14:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-72</guid>
		<description>[...] pensado para competir con DirectX 10 y no quiero meterme en el apartado técnico. Desarrollar con OpenGL 3 sera mas beneficioso para cualquier compañía que no este atada con contratos a sistemas cerrados, [...]</description>
		<content:encoded><![CDATA[<p>[...] pensado para competir con DirectX 10 y no quiero meterme en el apartado técnico. Desarrollar con OpenGL 3 sera mas beneficioso para cualquier compañía que no este atada con contratos a sistemas cerrados, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aras Pranckevičius</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-68</link>
		<dc:creator>Aras Pranckevičius</dc:creator>
		<pubDate>Mon, 19 May 2008 18:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-68</guid>
		<description>I don&#039;t mind D3D changing the API with each major revision. API itself is nothing; it&#039;s really easy to rewrite &quot;the same stuff&quot; to another API. Underlying hardware is still the same, so if the API is not Completely Stupid, it&#039;s not a big deal.

What I &lt;i&gt;do&lt;/i&gt; mind though, is whether API and everything related to it (drivers) &lt;i&gt;work&lt;/i&gt;. OpenGL fails miserably in this regard, with it&#039;s approach of &quot;let&#039;s let each IHV make their own bugs in the whole stack!&quot; it&#039;s just horrible. FBOs? GLSL? Argh!

Another thing that I don&#039;t mind that much is all the legacy APIs/extensions. There&#039;s probably ten ways to submit vertex data, while in fact there should be vertex buffers only. And even then, VBOs in GL don&#039;t match up what was available in D3D for years (updating a portion of VBO without additional memory copy, anyone?).

So in my view GL3 does not bring anything new to the table. Ok, maybe it will be simpler for IHVs to implement, which would take care of some bugs in the drivers. But what they should really do is force a common stack upon everyone, and make only the lowest-level driver be a responsibility of IHV.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t mind D3D changing the API with each major revision. API itself is nothing; it&#8217;s really easy to rewrite &#8220;the same stuff&#8221; to another API. Underlying hardware is still the same, so if the API is not Completely Stupid, it&#8217;s not a big deal.</p>
<p>What I <i>do</i> mind though, is whether API and everything related to it (drivers) <i>work</i>. OpenGL fails miserably in this regard, with it&#8217;s approach of &#8220;let&#8217;s let each IHV make their own bugs in the whole stack!&#8221; it&#8217;s just horrible. FBOs? GLSL? Argh!</p>
<p>Another thing that I don&#8217;t mind that much is all the legacy APIs/extensions. There&#8217;s probably ten ways to submit vertex data, while in fact there should be vertex buffers only. And even then, VBOs in GL don&#8217;t match up what was available in D3D for years (updating a portion of VBO without additional memory copy, anyone?).</p>
<p>So in my view GL3 does not bring anything new to the table. Ok, maybe it will be simpler for IHVs to implement, which would take care of some bugs in the drivers. But what they should really do is force a common stack upon everyone, and make only the lowest-level driver be a responsibility of IHV.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-67</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 19 May 2008 09:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-67</guid>
		<description>I think exactly the same to #Korval.
Every version of DirectX has the great disvantage of relying on a binary format for method calling and structs memory layout that is completely incompatible between major versions.
OpenGL has a smarter design in the sense of using raw C functions (instead of virtual C++ like methods) and almost no C structs.
But it is released with a functional equivalence to DX almost 2 years before. Otherways, using non-standar extensions is a nightmare. 
Current OpenGL version has a lot of inconsistences, and a lot of legacy unusefull methods.

But the modern design of DX is not the only advantage over OGL, but a consistent DirectX SDK with a compact documentation and a pletoria of examples.</description>
		<content:encoded><![CDATA[<p>I think exactly the same to #Korval.<br />
Every version of DirectX has the great disvantage of relying on a binary format for method calling and structs memory layout that is completely incompatible between major versions.<br />
OpenGL has a smarter design in the sense of using raw C functions (instead of virtual C++ like methods) and almost no C structs.<br />
But it is released with a functional equivalence to DX almost 2 years before. Otherways, using non-standar extensions is a nightmare.<br />
Current OpenGL version has a lot of inconsistences, and a lot of legacy unusefull methods.</p>
<p>But the modern design of DX is not the only advantage over OGL, but a consistent DirectX SDK with a compact documentation and a pletoria of examples.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Korval</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-60</link>
		<dc:creator>Korval</dc:creator>
		<pubDate>Fri, 16 May 2008 18:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-60</guid>
		<description>Nobody really says that GL 3.0 isn&#039;t important. But the fact is that it&#039;s too late. There was a pretty good window of opportunity for a new and improved GL API to swoop in and garner attention among PC game developers. That time has passed. Vista adoption is up, which means that D3D10 usage will be up. The break between Vista/XP and D3D10/9 (ie: if you use XP, you can&#039;t have D3D10 features) was a good opportunity that the ARB has squandered.

Furthermore, if the GL ARB couldn&#039;t get this done last year, why should we believe them this year? The fact is that the ARB has failed, monstrously. They did it before back when they were working on render-to-texture. They spent 2 years on something that shouldn&#039;t have taken more than 6. The younger GL programmers may not remember the days before VBO, but it took an awfully long time to get VBOs as well; until then, we had to rely on a bunch of vendor-specific extensions.

I love the ideas behind GL 3.0; I even wrote my GL 2.1-based rendering abstraction layer based on those ideas. But the fact is that it&#039;s very, very late. And even that wouldn&#039;t be so much of a problem if they could just tell us WHY it&#039;s late. But they won&#039;t. Which means it&#039;s either IP or some stupid argument about something that matters very little. And if it&#039;s the latter, then that means that the ARB is so worried about making a mistake that they won&#039;t actually produce anything. Which makes them ineffective.

For 1 year, the ARB was good about updating us on their progress. And then they stopped. That shows a blatant lack of respect for us the potential users of OpenGL. So why should we respect them back?</description>
		<content:encoded><![CDATA[<p>Nobody really says that GL 3.0 isn&#8217;t important. But the fact is that it&#8217;s too late. There was a pretty good window of opportunity for a new and improved GL API to swoop in and garner attention among PC game developers. That time has passed. Vista adoption is up, which means that D3D10 usage will be up. The break between Vista/XP and D3D10/9 (ie: if you use XP, you can&#8217;t have D3D10 features) was a good opportunity that the ARB has squandered.</p>
<p>Furthermore, if the GL ARB couldn&#8217;t get this done last year, why should we believe them this year? The fact is that the ARB has failed, monstrously. They did it before back when they were working on render-to-texture. They spent 2 years on something that shouldn&#8217;t have taken more than 6. The younger GL programmers may not remember the days before VBO, but it took an awfully long time to get VBOs as well; until then, we had to rely on a bunch of vendor-specific extensions.</p>
<p>I love the ideas behind GL 3.0; I even wrote my GL 2.1-based rendering abstraction layer based on those ideas. But the fact is that it&#8217;s very, very late. And even that wouldn&#8217;t be so much of a problem if they could just tell us WHY it&#8217;s late. But they won&#8217;t. Which means it&#8217;s either IP or some stupid argument about something that matters very little. And if it&#8217;s the latter, then that means that the ARB is so worried about making a mistake that they won&#8217;t actually produce anything. Which makes them ineffective.</p>
<p>For 1 year, the ARB was good about updating us on their progress. And then they stopped. That shows a blatant lack of respect for us the potential users of OpenGL. So why should we respect them back?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fldz</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-59</link>
		<dc:creator>fldz</dc:creator>
		<pubDate>Fri, 16 May 2008 17:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-59</guid>
		<description>I saw the word &quot;class&quot; somewhere in the specs or proposals, etc.  (I must&#039;ve passed out or put up a mental-block, so.. I wouldn&#039;t know where in the specs)

They would never go down that road even if they could &quot;support&quot; OOP, would they?

&quot;does not support the OOP (Object Oriented Programming) paradigm but a way around this is being implemented.&quot;

way around what, you mean speed? Flexibility perhaps? Imagination?

-a geek stuck in the 80&#039;s</description>
		<content:encoded><![CDATA[<p>I saw the word &#8220;class&#8221; somewhere in the specs or proposals, etc.  (I must&#8217;ve passed out or put up a mental-block, so.. I wouldn&#8217;t know where in the specs)</p>
<p>They would never go down that road even if they could &#8220;support&#8221; OOP, would they?</p>
<p>&#8220;does not support the OOP (Object Oriented Programming) paradigm but a way around this is being implemented.&#8221;</p>
<p>way around what, you mean speed? Flexibility perhaps? Imagination?</p>
<p>-a geek stuck in the 80&#8217;s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: E. Luten</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-57</link>
		<dc:creator>E. Luten</dc:creator>
		<pubDate>Fri, 16 May 2008 17:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-57</guid>
		<description>&lt;strong&gt;Lionel&lt;/strong&gt;, you&#039;re right but keep your eyes open during the next few months, I&#039;ve got a &lt;em&gt;good&lt;/em&gt; feeling that SIG08 will be the great turning point.</description>
		<content:encoded><![CDATA[<p><strong>Lionel</strong>, you&#8217;re right but keep your eyes open during the next few months, I&#8217;ve got a <em>good</em> feeling that SIG08 will be the great turning point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lionel Barret</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-56</link>
		<dc:creator>Lionel Barret</dc:creator>
		<pubDate>Fri, 16 May 2008 16:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-56</guid>
		<description>@E. Luten : I really hope it will be but in the past, Khronos/ARB have been so slow that I am not so sure.</description>
		<content:encoded><![CDATA[<p>@E. Luten : I really hope it will be but in the past, Khronos/ARB have been so slow that I am not so sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Geeks Of 3D » Why OpenGL 3.0 is Important</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-55</link>
		<dc:creator>The Geeks Of 3D » Why OpenGL 3.0 is Important</dc:creator>
		<pubDate>Fri, 16 May 2008 16:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-55</guid>
		<description>[...] post will attempt to take you through the pre-published materials on the OpenGL API, version 3.0 and [...]</description>
		<content:encoded><![CDATA[<p>[...] post will attempt to take you through the pre-published materials on the OpenGL API, version 3.0 and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: E. Luten</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-54</link>
		<dc:creator>E. Luten</dc:creator>
		<pubDate>Fri, 16 May 2008 16:36:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-54</guid>
		<description>&lt;strong&gt;@Lionel:&lt;/strong&gt; An update on OpenGL 3.0 will be made at the OpenGL BOF at SIGGRAPH 2008 this August. Judging that there&#039;s a year in between the last 3.0 announcement at SIGGRAPH 2007, this will probably be &lt;em&gt;it&lt;/em&gt;.</description>
		<content:encoded><![CDATA[<p><strong>@Lionel:</strong> An update on OpenGL 3.0 will be made at the OpenGL BOF at SIGGRAPH 2008 this August. Judging that there&#8217;s a year in between the last 3.0 announcement at SIGGRAPH 2007, this will probably be <em>it</em>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nerdd.net &#124; news and opinion</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-53</link>
		<dc:creator>nerdd.net &#124; news and opinion</dc:creator>
		<pubDate>Fri, 16 May 2008 08:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-53</guid>
		<description>&lt;strong&gt;Why OpenGL 3.0 is Important &#124; nerdd.net...&lt;/strong&gt;

\r\nWhen discussing OpenGL 3.0, one question of them keeps popping up: Why do we need OpenGL 3.0? Th...</description>
		<content:encoded><![CDATA[<p><strong>Why OpenGL 3.0 is Important | nerdd.net&#8230;</strong></p>
<p>\r\nWhen discussing OpenGL 3.0, one question of them keeps popping up: Why do we need OpenGL 3.0? Th&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lionel Barret</title>
		<link>http://blog.scriptionary.com/2008/05/15/why-opengl-30-is-important/comment-page-1/#comment-52</link>
		<dc:creator>Lionel Barret</dc:creator>
		<pubDate>Fri, 16 May 2008 07:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scriptionary.com/?p=21#comment-52</guid>
		<description>Sadly, the release date seems not very close. 

I don&#039;t follow closely the advancement (I should tho). Any info on that ?</description>
		<content:encoded><![CDATA[<p>Sadly, the release date seems not very close. </p>
<p>I don&#8217;t follow closely the advancement (I should tho). Any info on that ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
