<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: grinns</title><link>https://news.ycombinator.com/user?id=grinns</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 23 Apr 2026 12:14:51 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=grinns" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by grinns in "Google’s iron grip on Android: Controlling open source by any means necessary"]]></title><description><![CDATA[
<p>I think that you hear whatever you want to hear, but the truth is very different: Google's apps and APIs are just cloud endpoints and weaving them into AOSP doesn't make sense and just delays updates, as the same author previously scribbled: <a href="http://arstechnica.com/gadgets/2013/09/balky-carriers-and-slow-oems-step-aside-google-is-defragging-android" rel="nofollow">http://arstechnica.com/gadgets/2013/09/balky-carriers-and-sl...</a><p>As for "strong-arm tactics", what is referred to is explained in this post: <a href="http://officialandroid.blogspot.com/2012/09/the-benefits-importance-of-compatibility.html" rel="nofollow">http://officialandroid.blogspot.com/2012/09/the-benefits-imp...</a><p>As Andy Rubin puts it, Google will not encourage non compatible forks, it is in their interest to have Android developed apps run on all Android devices. Anyone can still have a go but Google won't encourage it.<p>It's a very flawed and overwritten attack piece, seemingly coming out of nowhere.</p>
]]></description><pubDate>Mon, 21 Oct 2013 07:29:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=6583905</link><dc:creator>grinns</dc:creator><comments>https://news.ycombinator.com/item?id=6583905</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=6583905</guid></item></channel></rss>