<?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"
	>
<channel>
	<title>Comments on: HTML&#8217;s Uncertain Future</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/</link>
	<description></description>
	<pubDate>Sat, 05 Jul 2008 21:46:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Oyun</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-627268</link>
		<dc:creator>Oyun</dc:creator>
		<pubDate>Wed, 06 Feb 2008 04:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-627268</guid>
		<description>I would remove a lot of the unused tags, and definitely no more frames or iframes, using AJAX and/or PHP to take care of that.</description>
		<content:encoded><![CDATA[<p>I would remove a lot of the unused tags, and definitely no more frames or iframes, using AJAX and/or PHP to take care of that.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: chris ward</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-101287</link>
		<dc:creator>chris ward</dc:creator>
		<pubDate>Tue, 21 Nov 2006 08:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-101287</guid>
		<description>@Etnu 

It's XAML to win the day, just wait til Microsoft push it with the platform! ;)
They've done it before and now they'll do it again.

Bet my career on it.</description>
		<content:encoded><![CDATA[<p>@Etnu </p>
<p>It&#8217;s XAML to win the day, just wait til Microsoft push it with the platform! ;)<br />
They&#8217;ve done it before and now they&#8217;ll do it again.</p>
<p>Bet my career on it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: hannson</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-96221</link>
		<dc:creator>hannson</dc:creator>
		<pubDate>Thu, 16 Nov 2006 16:20:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-96221</guid>
		<description>&lt;blockquote&gt;There’s nothing wrong with HTML at the moment.&lt;/blockquote&gt; 

But maybe we need to think ahead. I'd like to see more features but they are more related to the browsers rather than being HTML specific. For example, instead of using AJAX hacks to create a calendar/date drop down (like in Google Calendars) when a user has to type in a date - as a part of forms, it could have it's own drop down date-tag. Then you could style it like you want via CSS. 

But then again, introducing new tags like these will be dangerous for compatibility.</description>
		<content:encoded><![CDATA[<blockquote><p>There’s nothing wrong with HTML at the moment.</p></blockquote>
<p>But maybe we need to think ahead. I&#8217;d like to see more features but they are more related to the browsers rather than being HTML specific. For example, instead of using AJAX hacks to create a calendar/date drop down (like in Google Calendars) when a user has to type in a date - as a part of forms, it could have it&#8217;s own drop down date-tag. Then you could style it like you want via CSS. </p>
<p>But then again, introducing new tags like these will be dangerous for compatibility.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-95766</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Thu, 16 Nov 2006 06:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-95766</guid>
		<description>They can't even organize themselves, how are they going to write a specification for HTML? These guys are idiots. As if Microsoft will even adhere to the spec anyway. There's nothing wrong with HTML at the moment.</description>
		<content:encoded><![CDATA[<p>They can&#8217;t even organize themselves, how are they going to write a specification for HTML? These guys are idiots. As if Microsoft will even adhere to the spec anyway. There&#8217;s nothing wrong with HTML at the moment.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Conn</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-94035</link>
		<dc:creator>Chris Conn</dc:creator>
		<pubDate>Tue, 14 Nov 2006 20:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-94035</guid>
		<description>&lt;blockquote&gt;Ryan Bates said:
It’s pretty much impossible to build a mildly complex layout without resorting to CSS hacks or HTML tables—both are being used how they weren’t originally intended.&lt;/blockquote&gt;

The funny thing is that I doubt that cars were originially developed for killing people, but they sometimes are used specificially for that.  :)

Most browsers seem to have CSS turned on, but since Firefox allows me to turn it on/off at will (using Chris Pederick's WebDeveloper add-in), I do. That's the nice thing. If one wants a web site to be valid for older browsers and newer browsers, they can use a combination of these techniques dependent upon the browser's agent information. Thus, the web page can be custom built for each web browser as necessary (using appropriate server side scripts of course).
Imagine what those "poor" text only browsers are like ... uuuggghhh, my brain can't take that. Think about the crap they have to weed through.   :-P</description>
		<content:encoded><![CDATA[<blockquote><p>Ryan Bates said:<br />
It’s pretty much impossible to build a mildly complex layout without resorting to CSS hacks or HTML tables—both are being used how they weren’t originally intended.</p></blockquote>
<p>The funny thing is that I doubt that cars were originially developed for killing people, but they sometimes are used specificially for that.  :)</p>
<p>Most browsers seem to have CSS turned on, but since Firefox allows me to turn it on/off at will (using Chris Pederick&#8217;s WebDeveloper add-in), I do. That&#8217;s the nice thing. If one wants a web site to be valid for older browsers and newer browsers, they can use a combination of these techniques dependent upon the browser&#8217;s agent information. Thus, the web page can be custom built for each web browser as necessary (using appropriate server side scripts of course).<br />
Imagine what those &#8220;poor&#8221; text only browsers are like &#8230; uuuggghhh, my brain can&#8217;t take that. Think about the crap they have to weed through.   :-P</p>]]></content:encoded>
	</item>
	<item>
		<title>By: stridox</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-91239</link>
		<dc:creator>stridox</dc:creator>
		<pubDate>Sun, 12 Nov 2006 20:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-91239</guid>
		<description>I would remove a lot of the unused tags, and definitely no more frames or iframes, using AJAX and/or PHP to take care of that. 

@gostats
no blinking!</description>
		<content:encoded><![CDATA[<p>I would remove a lot of the unused tags, and definitely no more frames or iframes, using AJAX and/or PHP to take care of that. </p>
<p>@gostats<br />
no blinking!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Angnoe</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-91021</link>
		<dc:creator>Joshua Angnoe</dc:creator>
		<pubDate>Sun, 12 Nov 2006 15:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-91021</guid>
		<description>@Ryan Bates: Isn't that just what XML and XSLT does?</description>
		<content:encoded><![CDATA[<p>@Ryan Bates: Isn&#8217;t that just what XML and XSLT does?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: gostats</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-89817</link>
		<dc:creator>gostats</dc:creator>
		<pubDate>Sat, 11 Nov 2006 18:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-89817</guid>
		<description>I would like to see a tag which makes objects on the page blink.

....wait a minute</description>
		<content:encoded><![CDATA[<p>I would like to see a tag which makes objects on the page blink.</p>
<p>&#8230;.wait a minute</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Bates</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-88614</link>
		<dc:creator>Ryan Bates</dc:creator>
		<pubDate>Fri, 10 Nov 2006 17:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-88614</guid>
		<description>I would like to see HTML and CSS revamped together - or perhaps replaced entirely. Although they get the job done, the way the two relate to one another feels awkward. It's pretty much impossible to build a mildly complex layout without resorting to CSS hacks or HTML tables - both are being used how they weren't originally intended.

Perhaps HTML could be replaced completely by XML - no prespecified tags, you just organize the data how you want with custom tags. Then, CSS could be replaced with a more powerful layout language - kind of a mix between current HTML and CSS with a dash of a scripting language. This way it can take the XML data and have complete control on how it is displayed to the user.

This will never happen though. There is too much momentum behind the current technologies and it takes ages to make significant changes (will CSS 3 ever come?). On the bright side, server-side technologies seem to be moving faster which helps overcome some of the problems with the client-side languages.</description>
		<content:encoded><![CDATA[<p>I would like to see HTML and CSS revamped together - or perhaps replaced entirely. Although they get the job done, the way the two relate to one another feels awkward. It&#8217;s pretty much impossible to build a mildly complex layout without resorting to CSS hacks or HTML tables - both are being used how they weren&#8217;t originally intended.</p>
<p>Perhaps HTML could be replaced completely by XML - no prespecified tags, you just organize the data how you want with custom tags. Then, CSS could be replaced with a more powerful layout language - kind of a mix between current HTML and CSS with a dash of a scripting language. This way it can take the XML data and have complete control on how it is displayed to the user.</p>
<p>This will never happen though. There is too much momentum behind the current technologies and it takes ages to make significant changes (will CSS 3 ever come?). On the bright side, server-side technologies seem to be moving faster which helps overcome some of the problems with the client-side languages.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Yank</title>
		<link>http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-87842</link>
		<dc:creator>Kevin Yank</dc:creator>
		<pubDate>Fri, 10 Nov 2006 03:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2006/11/09/htmls-uncertain-future/#comment-87842</guid>
		<description>@HardCoded: From where I'm sitting, &lt;code&gt;&#60;separator&#62;&lt;/code&gt; is a semantically meaningful equivalent of &lt;code&gt;&#60;hr&#62;&lt;/code&gt;. Many narrative documents (e.g. novels) use a separator to cut between "scenes" or indicate a passage of time. This is a semantic element of the content, and does not imply any particular style or display (as the "horizontal rule" that gives &lt;code&gt;&#60;hr&#62;&lt;/code&gt; its name does).</description>
		<content:encoded><![CDATA[<p>@HardCoded: From where I&#8217;m sitting, <code>&lt;separator&gt;</code> is a semantically meaningful equivalent of <code>&lt;hr&gt;</code>. Many narrative documents (e.g. novels) use a separator to cut between &#8220;scenes&#8221; or indicate a passage of time. This is a semantic element of the content, and does not imply any particular style or display (as the &#8220;horizontal rule&#8221; that gives <code>&lt;hr&gt;</code> its name does).</p>]]></content:encoded>
	</item>
</channel>
</rss>
