<story><title>Tragedy of the WebKit Commons</title><url>http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.html</url></story><parent_chain></parent_chain><comment><author>erichocean</author><text>One problem I&apos;ve run into is not being able to submit bugs because my own codebase is relatively huge.[0]&lt;p&gt;For whatever reason, the bugs I see manifest as edge cases in  Chrome&apos;s new compositing system, but only under &quot;load&quot;. I&apos;ve tried to get small examples that show the bugs, and failed.&lt;p&gt;But since the developers will only accept tiny programs that demonstrate the problem, I&apos;m SOL.&lt;p&gt;UPDATE: Also, there&apos;s no such thing as &quot;WebKit&quot;, as though rendering issues, once fixed in &quot;WebKit&quot; are suddenly fixed as long as everyone updates to the last release. It doesn&apos;t work like that, because there are numerous rendering implementations built-on top of WebKit -- the ones I run into have to do with Chrome&apos;s compositor vs. Apple&apos;s compositor. They behave quite a bit differently, and those aren&apos;t the only two in use. The same is true of WebKit JavaScript engines and the APIs supported.&lt;p&gt;There&apos;s just no way, as a developer, to treat &quot;WebKit&quot; as a platform. You have to deal with every browser using WebKit separately.&lt;p&gt;[0] &lt;a href=&quot;https://github.com/erichocean/blossom&quot; rel=&quot;nofollow&quot;&gt;https://github.com/erichocean/blossom&lt;/a&gt;</text></comment>
<story><title>Tragedy of the WebKit Commons</title><url>http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.html</url></story><parent_chain></parent_chain><comment><author>dclowd9901</author><text>&amp;#62; Even when they have been fixed in the latest Chrome or Safari, older WebKit implementations like PhantomJS and UIWebView still don&apos;t have the fix. We&apos;ve had to put back several of these as users reported problems with the beta. It&apos;s starting to feel like oldIE all over again, but with a different set of excuses for why nothing can be fixed.&lt;p&gt;I am fairly new to web development, but this consistent droning (whining) about having to develop for a myriad of inconsistent platforms seems like braying from rather entitled web developers. I don&apos;t understand when in the history of software development developers weren&apos;t forced to dick with platform and legacy problems. Can someone explain what, if anything makes web dev different? And if they can&apos;t, can we please just stop bringing it up like it&apos;s ever been a new problem?</text></comment>