<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description></description><title>making time</title><generator>Tumblr (3.0; @qwang-blog)</generator><link>http://qwang.net/</link><item><title>Android &amp; it's hardware</title><description>&lt;p&gt;Why is Android so incompatible with it’s own hardware?&lt;/p&gt;
&lt;p&gt;When v2.3 came out, it took Google months to port the update onto the Nexus One.  This is supposed to be a pure, unskinned, 100% Google experience, on their own reference hardware.  So why was a “port” necessary?  It happened again with Ice Cream Sandwich for the Nexus S.&lt;/p&gt;
&lt;p&gt;Why is this happening?  The Windows ecosystem is arguably even more of a Galapagos of distinct hardware species, yet when Windows 7 came out, you could reasonably expect it to work on any PC in the world currently on Vista or XP.&lt;/p&gt;</description><link>http://qwang.net/post/14837023986</link><guid>http://qwang.net/post/14837023986</guid><pubDate>Mon, 26 Dec 2011 17:32:00 -0800</pubDate><dc:creator>qdub</dc:creator></item></channel></rss>

