<?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: The Stinger</title>
	<atom:link href="http://meyerweb.com/eric/thoughts/2013/03/04/the-stinger/feed/" rel="self" type="application/rss+xml" />
	<link>http://meyerweb.com/eric/thoughts/2013/03/04/the-stinger/</link>
	<description>Things that Eric A. Meyer, CSS expert, writes about on his personal Web site; it&#039;s largely Web standards and Web technology, but also various bits of culture, politics, personal observations, and other miscellaneous stuff</description>
	<lastBuildDate>Fri, 10 May 2013 11:50:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Eric Meyer</title>
		<link>http://meyerweb.com/eric/thoughts/2013/03/04/the-stinger/#comment-1216450</link>
		<dc:creator>Eric Meyer</dc:creator>
		<pubDate>Mon, 04 Mar 2013 20:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=2155#comment-1216450</guid>
		<description><![CDATA[I hear you, Tom.  I too was sorry to see Presto go, and there are still (perhaps always will be) problems with developers succumbing to tunnel vision, as they have with WebKit.  The difference now is that there are many, many voices pushing back to represent a better path.  When the WaSP was founded, it was nearly alone in advocating for web standards.  Now there are thousands upon thousands who have taken up that banner.

You’re clearly one of them, so thank you.  Keep fighting that fight!  You and all the people like you (and I hope I am one of them) make it possible for the WaSP to retire with grace, confident that the message will continue.]]></description>
		<content:encoded><![CDATA[<p>I hear you, Tom.  I too was sorry to see Presto go, and there are still (perhaps always will be) problems with developers succumbing to tunnel vision, as they have with WebKit.  The difference now is that there are many, many voices pushing back to represent a better path.  When the WaSP was founded, it was nearly alone in advocating for web standards.  Now there are thousands upon thousands who have taken up that banner.</p>
<p>You’re clearly one of them, so thank you.  Keep fighting that fight!  You and all the people like you (and I hope I am one of them) make it possible for the WaSP to retire with grace, confident that the message will continue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom jones</title>
		<link>http://meyerweb.com/eric/thoughts/2013/03/04/the-stinger/#comment-1216425</link>
		<dc:creator>tom jones</dc:creator>
		<pubDate>Mon, 04 Mar 2013 19:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://meyerweb.com/eric/thoughts/?p=2155#comment-1216425</guid>
		<description><![CDATA[&quot;These last years have shown that the job is in very good hands.&quot;

i find this whole thing very ironic, as it&#039;s occurring in the same month as we lost 25% of diversity in rendering engines.

and that happened precisely because developers aren&#039;t doing &quot;their job&quot;, because mobile sites (and apps) are written not for the web (standards), but for webkit.

the dominance of webkit on mobile, both in user numbers and developer mindshare (or &quot;being developed for&quot;, or &quot;this site best viewed on..&quot;) is approaching IE6 numbers. what&#039;s worse, the situation is even more dire than 10 years ago, as we can&#039;t even hope for another alternative to grow up (like Firefox did) on the dominant mobile platform (it&#039;s prohibited).

and this is when they decide to shut down the project? &quot;not paying attention&quot; is putting it mildly..
http://blog.gerv.net/2013/03/web-standards-project-shuts-not-paying-attention]]></description>
		<content:encoded><![CDATA[<p>&#8220;These last years have shown that the job is in very good hands.&#8221;</p>
<p>i find this whole thing very ironic, as it&#8217;s occurring in the same month as we lost 25% of diversity in rendering engines.</p>
<p>and that happened precisely because developers aren&#8217;t doing &#8220;their job&#8221;, because mobile sites (and apps) are written not for the web (standards), but for webkit.</p>
<p>the dominance of webkit on mobile, both in user numbers and developer mindshare (or &#8220;being developed for&#8221;, or &#8220;this site best viewed on..&#8221;) is approaching IE6 numbers. what&#8217;s worse, the situation is even more dire than 10 years ago, as we can&#8217;t even hope for another alternative to grow up (like Firefox did) on the dominant mobile platform (it&#8217;s prohibited).</p>
<p>and this is when they decide to shut down the project? &#8220;not paying attention&#8221; is putting it mildly..<br />
<a href="http://blog.gerv.net/2013/03/web-standards-project-shuts-not-paying-attention" rel="nofollow">http://blog.gerv.net/2013/03/web-standards-project-shuts-not-paying-attention</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->