<?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: Is Weightwatchers a Victim of the Current Web Browser War?</title>
	<atom:link href="http://blog.cre8asite.net/bwelford/2004/11/is-weightwatchers-a-victim-of-the-current-web-browser-war/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cre8asite.net/bwelford/2004/11/is-weightwatchers-a-victim-of-the-current-web-browser-war/</link>
	<description>Internet Marketing And SEO From A Different Point Of View</description>
	<pubDate>Tue, 06 Jan 2009 06:33:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BWelford</title>
		<link>http://blog.cre8asite.net/bwelford/2004/11/is-weightwatchers-a-victim-of-the-current-web-browser-war/comment-page-1/#comment-16</link>
		<dc:creator>BWelford</dc:creator>
		<pubDate>Fri, 26 Nov 2004 06:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cre8asite.net/bwelford/archive/196#comment-16</guid>
		<description>I agree, Diane.  Microsoft's approach is backwards.  I would even go stronger and say it's nonsense.  It may sound OK as it washes over you, but if you really examine what they're saying, it will cause them increasing grief.  Currently a certain percentage of people have a problem with the chaotic reasoning of Microsoft Internet Explorer.  When they're in a dominant majority position, they can say, "If you have a problem then it's up to you to solve it".  That won't last for ever and how do they cope with that change when it comes.  The longer they leave it, the worse it gets.</description>
		<content:encoded><![CDATA[<p>I agree, Diane.  Microsoft&#8217;s approach is backwards.  I would even go stronger and say it&#8217;s nonsense.  It may sound OK as it washes over you, but if you really examine what they&#8217;re saying, it will cause them increasing grief.  Currently a certain percentage of people have a problem with the chaotic reasoning of Microsoft Internet Explorer.  When they&#8217;re in a dominant majority position, they can say, &#8220;If you have a problem then it&#8217;s up to you to solve it&#8221;.  That won&#8217;t last for ever and how do they cope with that change when it comes.  The longer they leave it, the worse it gets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DianeV</title>
		<link>http://blog.cre8asite.net/bwelford/2004/11/is-weightwatchers-a-victim-of-the-current-web-browser-war/comment-page-1/#comment-15</link>
		<dc:creator>DianeV</dc:creator>
		<pubDate>Fri, 26 Nov 2004 05:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cre8asite.net/bwelford/archive/196#comment-15</guid>
		<description>Microsoft has somewhat spun this to be complimentary to itself.  The fact is that it's one thing to make a browser that overlooks some types of coding errors (e.g., unclosed table tags) and is backwards compatible.  It's quite another to double specified margin sizes and other IE tricks.  How is that "backwards compatible"?

They can claim all they like that they're supporting their market, and that their market "expects" it.  Frankly, I find that most people don't know what a browser is; they simply click on the "e".  (So they tell me, in fact.)  I further think they're being fairly cynical about their own FrontPage market; how are these people to know that they may be coding for Microsoft rather than the Internet?

Frankly, creating websites is something like controling a VCR, or driving a car (if less dangerous):  bottom line is that you actually have to learn something.  Better to learn it than to have it all masked from you, with embarrassing errors galore.

I'm not suggesting that everyone must adopt Web Standards coding now.  Frankly, I don't see that even all of the better current browsers display identically and/or completely correctly.  Not ready for the commercial prime time, where web designers have to develop unbreakable sites.  What I'm suggesting is learning a few things, and having the currently major browser support CORRECT coding correctly.

No, I'm afraid that the only thing backwards here is Microsoft's approach.  Luckily, not all countries are going Microsoft ...</description>
		<content:encoded><![CDATA[<p>Microsoft has somewhat spun this to be complimentary to itself.  The fact is that it&#8217;s one thing to make a browser that overlooks some types of coding errors (e.g., unclosed table tags) and is backwards compatible.  It&#8217;s quite another to double specified margin sizes and other IE tricks.  How is that &#8220;backwards compatible&#8221;?</p>
<p>They can claim all they like that they&#8217;re supporting their market, and that their market &#8220;expects&#8221; it.  Frankly, I find that most people don&#8217;t know what a browser is; they simply click on the &#8220;e&#8221;.  (So they tell me, in fact.)  I further think they&#8217;re being fairly cynical about their own FrontPage market; how are these people to know that they may be coding for Microsoft rather than the Internet?</p>
<p>Frankly, creating websites is something like controling a VCR, or driving a car (if less dangerous):  bottom line is that you actually have to learn something.  Better to learn it than to have it all masked from you, with embarrassing errors galore.</p>
<p>I&#8217;m not suggesting that everyone must adopt Web Standards coding now.  Frankly, I don&#8217;t see that even all of the better current browsers display identically and/or completely correctly.  Not ready for the commercial prime time, where web designers have to develop unbreakable sites.  What I&#8217;m suggesting is learning a few things, and having the currently major browser support CORRECT coding correctly.</p>
<p>No, I&#8217;m afraid that the only thing backwards here is Microsoft&#8217;s approach.  Luckily, not all countries are going Microsoft &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
