<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Web Development from Thinking and Making</title>
    <link>http://future.ourpublicsquare.com/</link>
    <pubDate>Tue, 18 Dec 2007 04:13:00 GMT</pubDate>
    <description>Stories on Web Development from Thinking and Making</description>
    <item>
      <title>Web standards didn't kill HTML</title>
      <link>http://future.ourpublicsquare.com/view/web-standards-didnt</link>
      <guid>http://future.ourpublicsquare.com/view/web-standards-didnt</guid>
      <description>&lt;redirect url="http://thinkingandmaking.com/notes/265/"&gt;

&lt;p&gt;There's some noise floating around about how web standards have destroyed the web. The argument goes like this:&lt;/p&gt;

&lt;p&gt;1. We haven't anything new and cool in ages (implementing new features).&lt;/p&gt;

&lt;p&gt;2. We haven't even had anything old and cool in ages (finally implementing old specs).&lt;/p&gt;

&lt;p&gt;3. This is because of web standards.&lt;/p&gt;

&lt;p&gt;This seems pretty silly to me. Web standards never said browser developers couldn't come up with crazy new, proprietary features. And, standards advocates never said browser makers had to implement all of the spec.&lt;/p&gt;

&lt;p&gt;The web standards goal was that if browser makers would implement some standard in a standard way, then the web would be a better more accessible, easier to create, and easier to maintain.&lt;/p&gt;

&lt;p&gt;And they were right.&lt;/p&gt;

&lt;p&gt;If you're pissed you aren't getting enough new markup toys this Christmas, go yell at the toy makers.&lt;/p&gt;</description>
      <pubDate>Tue, 18 Dec 2007 04:13:00 GMT</pubDate>
      <author>Austin Govella</author>
      <category>Web Development</category>
    </item>
  </channel>
</rss>
