<?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: Browser 2.0</title>
	<atom:link href="http://www.centernetworks.com/browser-2-0/feed" rel="self" type="application/rss+xml" />
	<link>http://www.centernetworks.com/browser-2-0</link>
	<description>Web 2 and Social Media News and Reviews</description>
	<lastBuildDate>Sat, 21 Nov 2009 01:50:56 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Till</title>
		<link>http://www.centernetworks.com/browser-2-0/comment-page-#comment-11149</link>
		<dc:creator>Till</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-11149</guid>
		<description>While the concept to create a unified stanard is not exactly new - there is the W3C and many standards to adhere to - I was wondering, is &quot;Browser 2.0&quot; your personal proposal to end the struggle or are you referring to someone else&#039; proposal (Where is the link? ;-))?

I think in general that while for example Microsoft both &quot;enhanced&quot; and neglected the standard for years at the same time, with IE7 they are finally moving into another direction.

If you follow the IE7 blog you see how much they talk about bugfixes (CSS, XHTML, ...) and that is good. At last! And it is because people made them to, not because of some new company policy. 

Having said all that, what would &quot;Browser 2.0&quot; do for me? Why not instead support the W3C and all the work already done?

I mean, even if for example Safari would be the only browser to support CSS3 - so be it. As long as it&#039;s done according to the standards, let them implement whatever they want, people can use it and build on it and &quot;rely on it&quot; which is common Intranet environments.

I think the problems we see today are not because of what is implemented, but rather how.</description>
		<content:encoded><![CDATA[<p>While the concept to create a unified stanard is not exactly new &#8211; there is the W3C and many standards to adhere to &#8211; I was wondering, is &#8220;Browser 2.0&#8243; your personal proposal to end the struggle or are you referring to someone else&#8217; proposal (Where is the link? ;-))?</p>
<p>I think in general that while for example Microsoft both &#8220;enhanced&#8221; and neglected the standard for years at the same time, with IE7 they are finally moving into another direction.</p>
<p>If you follow the IE7 blog you see how much they talk about bugfixes (CSS, XHTML, &#8230;) and that is good. At last! And it is because people made them to, not because of some new company policy. </p>
<p>Having said all that, what would &#8220;Browser 2.0&#8243; do for me? Why not instead support the W3C and all the work already done?</p>
<p>I mean, even if for example Safari would be the only browser to support CSS3 &#8211; so be it. As long as it&#8217;s done according to the standards, let them implement whatever they want, people can use it and build on it and &#8220;rely on it&#8221; which is common Intranet environments.</p>
<p>I think the problems we see today are not because of what is implemented, but rather how.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JakeDahn</title>
		<link>http://www.centernetworks.com/browser-2-0/comment-page-#comment-11150</link>
		<dc:creator>JakeDahn</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-11150</guid>
		<description>I&#039;m highly aware of W3C, and I really do support them. The only problem is that there are browsers, like IE, which do not follow the standards. I think that IE7 is going to be a little more standards focussed, but I still think that there will be a struggle between mainstream standards, and what microsoft says are standards.  the whole &quot;Browser 2.0&quot; idea was inspired by what the original aim of this article was focused at. I really wanted to to evaluate the effect of certain browsers, on web 2.0, but the article turned out being more of a &quot;We need better standards!&quot; kind of post.   I have nothing against W3C, I support the fully. The only thing that is bothersome, is when a browser or company says, screw that, I&#039;ll do my own thing. This is what happened with IE. I think that we need to somehow, enforce the standards, as they come out. So right now Safari supports CSS3, I think that all the other browsers should support the same standards.  You said &quot;I think the problems we see today are not because of what is implemented, but rather how.&quot; I really agree with this, as you say the problems today. But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented. I think that most browsers will get the idea, as how to implement things, but they will often be outdated. I wouldn&#039;t be surprised if IE8 will come after IE7 is really really outdated.</description>
		<content:encoded><![CDATA[<p>I&#39;m highly aware of W3C, and I really do support them. The only problem is that there are browsers, like IE, which do not follow the standards. I think that IE7 is going to be a little more standards focussed, but I still think that there will be a struggle between mainstream standards, and what microsoft says are standards.  the whole &quot;Browser 2.0&quot; idea was inspired by what the original aim of this article was focused at. I really wanted to to evaluate the effect of certain browsers, on web 2.0, but the article turned out being more of a &quot;We need better standards!&quot; kind of post.   I have nothing against W3C, I support the fully. The only thing that is bothersome, is when a browser or company says, screw that, I&#39;ll do my own thing. This is what happened with IE. I think that we need to somehow, enforce the standards, as they come out. So right now Safari supports CSS3, I think that all the other browsers should support the same standards.  You said &quot;I think the problems we see today are not because of what is implemented, but rather how.&quot; I really agree with this, as you say the problems today. But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented. I think that most browsers will get the idea, as how to implement things, but they will often be outdated. I wouldn&#39;t be surprised if IE8 will come after IE7 is really really outdated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: till</title>
		<link>http://www.centernetworks.com/browser-2-0/comment-page-#comment-11155</link>
		<dc:creator>till</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-11155</guid>
		<description>&lt;cite&gt;But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented.&lt;/cite&gt;

Not sure I fully agree with you on this, but I can see your point.

For me (as a developer) it&#039;s more along the lines of, that I &quot;wish&quot; all browsers would support (for example) CSS2 but also to the full extend of the language and of course according to all standards.

Then I would be able to build websites that work everywhere and do not rely on browser tweaks and switches. So for me the so called &quot;next generation&quot; is not as important as what&#039;s going on now. I&#039;d rather see all browsers support CSS2 completely before some take on CSS3.</description>
		<content:encoded><![CDATA[<p><cite>But the problems of tomorrow (after IE7 is out), the problem will be when things are implemented.</cite></p>
<p>Not sure I fully agree with you on this, but I can see your point.</p>
<p>For me (as a developer) it&#8217;s more along the lines of, that I &#8220;wish&#8221; all browsers would support (for example) CSS2 but also to the full extend of the language and of course according to all standards.</p>
<p>Then I would be able to build websites that work everywhere and do not rely on browser tweaks and switches. So for me the so called &#8220;next generation&#8221; is not as important as what&#8217;s going on now. I&#8217;d rather see all browsers support CSS2 completely before some take on CSS3.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
