<?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: Comic Update: Opera&#8217;s Rough Edges</title>
	<atom:link href="http://cssquirrel.com/2009/11/16/comic-update-operas-rough-edges/feed/" rel="self" type="application/rss+xml" />
	<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/</link>
	<description>opinions and news on web design</description>
	<lastBuildDate>Thu, 17 May 2012 05:41:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cesar</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-31365</link>
		<dc:creator>Cesar</dc:creator>
		<pubDate>Mon, 18 Jan 2010 18:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-31365</guid>
		<description>Ohh...the irony, the guys working behind Opera are also behind the W3C CSS Spec, it&#039;s incredible!
Nice comic btw, got a good laugh out of it :D</description>
		<content:encoded><![CDATA[<p>Ohh&#8230;the irony, the guys working behind Opera are also behind the W3C CSS Spec, it&#8217;s incredible!<br />
Nice comic btw, got a good laugh out of it :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Low Down On Cascading Style Sheets &#124; Web Design and all stuff related to it!</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30714</link>
		<dc:creator>The Low Down On Cascading Style Sheets &#124; Web Design and all stuff related to it!</dc:creator>
		<pubDate>Wed, 25 Nov 2009 19:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30714</guid>
		<description>[...] CSSquirrel : Comic Update: Opera&#039;s Rough Edges: Kyle Weems [...]</description>
		<content:encoded><![CDATA[<p>[...] CSSquirrel : Comic Update: Opera&#39;s Rough Edges: Kyle Weems [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VeoSotano</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30338</link>
		<dc:creator>VeoSotano</dc:creator>
		<pubDate>Thu, 19 Nov 2009 17:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30338</guid>
		<description>@Kyle - That&#039;s only for the plug-ins that require support to view ANY content. In my plan, since all the content (which, e.g. your search engine spider will be able to read) is written in XML -plain text-, those users who have a browser with no plug-in architecture will still be able to access all the content. Just not the rendering.

Using a plug-in has the distinct advantage that you can support all browsers with a plug-in architecture - heck, even IE6! - and the rendered output will look and behave exactly the same on all plattforms (well, not everywhere. It&#039;s not the same a desktop pc with a large screen or a smartphone with touchscreen, but that will be solved by means of profiles (á la CSS-media rules) and other cool features).</description>
		<content:encoded><![CDATA[<p>@Kyle &#8211; That&#8217;s only for the plug-ins that require support to view ANY content. In my plan, since all the content (which, e.g. your search engine spider will be able to read) is written in XML -plain text-, those users who have a browser with no plug-in architecture will still be able to access all the content. Just not the rendering.</p>
<p>Using a plug-in has the distinct advantage that you can support all browsers with a plug-in architecture &#8211; heck, even IE6! &#8211; and the rendered output will look and behave exactly the same on all plattforms (well, not everywhere. It&#8217;s not the same a desktop pc with a large screen or a smartphone with touchscreen, but that will be solved by means of profiles (á la CSS-media rules) and other cool features).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Weems</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30278</link>
		<dc:creator>Kyle Weems</dc:creator>
		<pubDate>Wed, 18 Nov 2009 17:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30278</guid>
		<description>@VeoSotano - Well, to start with, using a browser plug-in as the basis for a new presentational technique is a recipe for disaster for anyone who uses a browser that doesn&#039;t support the plug-in. 

I personally am not an expert enough on the topic to say whether such a technology would be superior to the current standards, or even if it was, how easy it would be to learn and deploy. But in general, most good ideas start as crazy ones.</description>
		<content:encoded><![CDATA[<p>@VeoSotano &#8211; Well, to start with, using a browser plug-in as the basis for a new presentational technique is a recipe for disaster for anyone who uses a browser that doesn&#8217;t support the plug-in. </p>
<p>I personally am not an expert enough on the topic to say whether such a technology would be superior to the current standards, or even if it was, how easy it would be to learn and deploy. But in general, most good ideas start as crazy ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VeoSotano</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30216</link>
		<dc:creator>VeoSotano</dc:creator>
		<pubDate>Tue, 17 Nov 2009 22:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30216</guid>
		<description>@Kyle What do you think, how would the webosphere react to a new (and in my view, far superior) technology, deployed as a browser plug-in? Would they opose it just because it is something different than HTML5?

I&#039;m going to let out just a little bit: What I call XHS is a combination of two technologies: a new language whose syntax is derived from CSS, called HSS (Hierarchical Style Sheets) and good ol&#039; XML for the content. The publishing of the web documents remain plain text files, and it will be an open standard every can code for. The document will be displayed using a browser plug-in, developed by the open source community.</description>
		<content:encoded><![CDATA[<p>@Kyle What do you think, how would the webosphere react to a new (and in my view, far superior) technology, deployed as a browser plug-in? Would they opose it just because it is something different than HTML5?</p>
<p>I&#8217;m going to let out just a little bit: What I call XHS is a combination of two technologies: a new language whose syntax is derived from CSS, called HSS (Hierarchical Style Sheets) and good ol&#8217; XML for the content. The publishing of the web documents remain plain text files, and it will be an open standard every can code for. The document will be displayed using a browser plug-in, developed by the open source community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Weems</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30215</link>
		<dc:creator>Kyle Weems</dc:creator>
		<pubDate>Tue, 17 Nov 2009 22:17:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30215</guid>
		<description>VeoSotano. Right. Sorry. I was typing too fast. :)</description>
		<content:encoded><![CDATA[<p>VeoSotano. Right. Sorry. I was typing too fast. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VeoSotano</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30214</link>
		<dc:creator>VeoSotano</dc:creator>
		<pubDate>Tue, 17 Nov 2009 22:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30214</guid>
		<description>Hey, it&#039;s NOT VeoSanto!!!</description>
		<content:encoded><![CDATA[<p>Hey, it&#8217;s NOT VeoSanto!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Weems</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30213</link>
		<dc:creator>Kyle Weems</dc:creator>
		<pubDate>Tue, 17 Nov 2009 21:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30213</guid>
		<description>@VeoSanto - I pull the avatars from http://www.gravatar.com/. You associate an image with the email address that you use when writing your comment, and it will pull that image instead of the default acorn.</description>
		<content:encoded><![CDATA[<p>@VeoSanto &#8211; I pull the avatars from <a href="http://www.gravatar.com/" rel="nofollow">http://www.gravatar.com/</a>. You associate an image with the email address that you use when writing your comment, and it will pull that image instead of the default acorn.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VeoSotano</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30205</link>
		<dc:creator>VeoSotano</dc:creator>
		<pubDate>Tue, 17 Nov 2009 19:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30205</guid>
		<description>@Kyle: look at it this way, WebKit is advancing rendering capabilities like no other browser (transforms, animations, 3d, etc), but those features won&#039;t be put to use until years after, or even never, just because other browsers don&#039;t jump on board. Actually, we&#039;re already bound to a single gateway for features, namely the W3C. It&#039;s just because of the different levels of implementation of each browser that we have this mess.

I propose an open source project, like WebKit, but where everybody&#039;s contribution adds to the web as a whole. This way, browser makers could stop wasting time in reinventing the wheel, and focus on what makes their software special. And authors know exactaly what they can expect in how their pages will be rendered.

This is part of a project of mine, which, if everything goes as planned, will change the web forever. Next to it, HTML+CSS will look like we&#039;ve been living in the stone age :) If you want to have a chat, and want me to tell you more about it, well you have my email address ;)

And by the way, it is VeoSotano, not VeoSanto ;)

Cheers

P.D. How can I have my custom avatar? If I get one, I&#039;ll stop by and add to the conversation more often, I promise :D</description>
		<content:encoded><![CDATA[<p>@Kyle: look at it this way, WebKit is advancing rendering capabilities like no other browser (transforms, animations, 3d, etc), but those features won&#8217;t be put to use until years after, or even never, just because other browsers don&#8217;t jump on board. Actually, we&#8217;re already bound to a single gateway for features, namely the W3C. It&#8217;s just because of the different levels of implementation of each browser that we have this mess.</p>
<p>I propose an open source project, like WebKit, but where everybody&#8217;s contribution adds to the web as a whole. This way, browser makers could stop wasting time in reinventing the wheel, and focus on what makes their software special. And authors know exactaly what they can expect in how their pages will be rendered.</p>
<p>This is part of a project of mine, which, if everything goes as planned, will change the web forever. Next to it, HTML+CSS will look like we&#8217;ve been living in the stone age :) If you want to have a chat, and want me to tell you more about it, well you have my email address ;)</p>
<p>And by the way, it is VeoSotano, not VeoSanto ;)</p>
<p>Cheers</p>
<p>P.D. How can I have my custom avatar? If I get one, I&#8217;ll stop by and add to the conversation more often, I promise :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arpit Jacob</title>
		<link>http://cssquirrel.com/blog/2009/11/16/comic-update-operas-rough-edges/comment-page-1/#comment-30203</link>
		<dc:creator>Arpit Jacob</dc:creator>
		<pubDate>Tue, 17 Nov 2009 18:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=496#comment-30203</guid>
		<description>:) anything is better than IE</description>
		<content:encoded><![CDATA[<p>:) anything is better than IE</p>
]]></content:encoded>
	</item>
</channel>
</rss>

