<?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: Thoughts on SlimDX 2</title>
	<atom:link href="http://scientificninja.com/blog/thoughts-on-slimdx-2/feed" rel="self" type="application/rss+xml" />
	<link>http://scientificninja.com/blog/thoughts-on-slimdx-2</link>
	<description></description>
	<lastBuildDate>Sat, 28 Aug 2010 22:47:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Rim</title>
		<link>http://scientificninja.com/blog/thoughts-on-slimdx-2/comment-page-1#comment-153</link>
		<dc:creator>Rim</dc:creator>
		<pubDate>Tue, 09 Mar 2010 09:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://scientificninja.com/?p=735#comment-153</guid>
		<description>&lt;p&gt;Assuming you don&#039;t go timebombing your releases you&#039;ll still have MDX beat on the compatibility front&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Assuming you don&#8217;t go timebombing your releases you&#8217;ll still have MDX beat on the compatibility front</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Petrie</title>
		<link>http://scientificninja.com/blog/thoughts-on-slimdx-2/comment-page-1#comment-121</link>
		<dc:creator>Josh Petrie</dc:creator>
		<pubDate>Thu, 04 Mar 2010 18:09:03 +0000</pubDate>
		<guid isPermaLink="false">http://scientificninja.com/?p=735#comment-121</guid>
		<description>&lt;p&gt;Well, there will definitely be a slew of breaking changes in SlimDX 2, that&#039;s part of why we want to start talking about things as early as possible -- so developers have some idea of the scope of the changes they&#039;d need to make to upgrade to 2.0. We plan on continuing development of the 1.0 codeline such that there is significant concurrent development overlap between the two versions. We want to enable developers to migrate to 2.0 on &lt;em&gt;their&lt;/em&gt; schedule and not &lt;em&gt;ours&lt;/em&gt;. Probably the only thing we wouldn&#039;t add to 1.0 after 2.0 ships are entirely new APIs, like Direct3D 12 or something.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well, there will definitely be a slew of breaking changes in SlimDX 2, that&#8217;s part of why we want to start talking about things as early as possible &#8212; so developers have some idea of the scope of the changes they&#8217;d need to make to upgrade to 2.0. We plan on continuing development of the 1.0 codeline such that there is significant concurrent development overlap between the two versions. We want to enable developers to migrate to 2.0 on <em>their</em> schedule and not <em>ours</em>. Probably the only thing we wouldn&#8217;t add to 1.0 after 2.0 ships are entirely new APIs, like Direct3D 12 or something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rim</title>
		<link>http://scientificninja.com/blog/thoughts-on-slimdx-2/comment-page-1#comment-119</link>
		<dc:creator>Rim</dc:creator>
		<pubDate>Thu, 04 Mar 2010 05:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://scientificninja.com/?p=735#comment-119</guid>
		<description>&lt;p&gt;Well, unlike some other Managed DirectX libraries at least you didn&#039;t release a version 1.1 that replaced all getX/setX methods with properties because you forgot to use those in the first place. You beat Microsoft&#039;s compatibility promise bigtime&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Well, unlike some other Managed DirectX libraries at least you didn&#8217;t release a version 1.1 that replaced all getX/setX methods with properties because you forgot to use those in the first place. You beat Microsoft&#8217;s compatibility promise bigtime</p>
]]></content:encoded>
	</item>
</channel>
</rss>
