<?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: JavaScript is now &#8220;Standard&#8221;</title>
	<atom:link href="http://wordsoftheweb.com/2009/12/javascript-is-now-standard/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 19:04:12 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bruce</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-87</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 19 May 2010 16:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-87</guid>
		<description>Facebook is a bad example, very few website owners can or should compare themselves to a company/site like that simply because they&#039;re worlds apart.

Judgments on your site technology support should be made on an individual basis depending on the site and its visitors. If like me you work with very corporate companies where JS is all too likely to be disabled by a paranoid sys admins (and IE is used by 90%+ users… *sigh*) then it would be foolish not to make sure the site works with JS disabled. 

As I have already mentioned on Twatter as far as I&#039;m concerned Javascript should — in most cases — be used as a layer to enhance content, just like CSS. Relying on JS for vital elements of a site such as its content is to rely on yet another technology, another possible weak spot.

Of course if 98% of your visitors have JS enabled then go crazy all you like with it! :)</description>
		<content:encoded><![CDATA[<p>Facebook is a bad example, very few website owners can or should compare themselves to a company/site like that simply because they&#8217;re worlds apart.</p>
<p>Judgments on your site technology support should be made on an individual basis depending on the site and its visitors. If like me you work with very corporate companies where JS is all too likely to be disabled by a paranoid sys admins (and IE is used by 90%+ users… *sigh*) then it would be foolish not to make sure the site works with JS disabled. </p>
<p>As I have already mentioned on Twatter as far as I&#8217;m concerned Javascript should — in most cases — be used as a layer to enhance content, just like CSS. Relying on JS for vital elements of a site such as its content is to rely on yet another technology, another possible weak spot.</p>
<p>Of course if 98% of your visitors have JS enabled then go crazy all you like with it! <img src='http://wordsoftheweb.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abstract art</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-84</link>
		<dc:creator>abstract art</dc:creator>
		<pubDate>Sat, 01 May 2010 08:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-84</guid>
		<description>I enjoyed checking out your blog today and I will be back to check it more in the future so please keep up your good quality work. I love the colors that you chose, you are quite talented!</description>
		<content:encoded><![CDATA[<p>I enjoyed checking out your blog today and I will be back to check it more in the future so please keep up your good quality work. I love the colors that you chose, you are quite talented!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sham</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-76</link>
		<dc:creator>Paul Sham</dc:creator>
		<pubDate>Thu, 03 Dec 2009 01:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-76</guid>
		<description>&quot;it has been agreed&quot; makes it sound like there is some overarching consensus about it. You should have said &quot;we agreed&quot;. Anyways, that&#039;s just a minor thing.

I still agree with Ryan in that your website should not rely on Javascript. At the very least, include some noscript tags. At best, make your sites degrade nicely.</description>
		<content:encoded><![CDATA[<p>&#8220;it has been agreed&#8221; makes it sound like there is some overarching consensus about it. You should have said &#8220;we agreed&#8221;. Anyways, that&#8217;s just a minor thing.</p>
<p>I still agree with Ryan in that your website should not rely on Javascript. At the very least, include some noscript tags. At best, make your sites degrade nicely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-75</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 02 Dec 2009 23:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-75</guid>
		<description>Ah ok :)</description>
		<content:encoded><![CDATA[<p>Ah ok <img src='http://wordsoftheweb.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carson</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-74</link>
		<dc:creator>Carson</dc:creator>
		<pubDate>Wed, 02 Dec 2009 23:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-74</guid>
		<description>I agree, Ryan, that corporate company websites don&#039;t need JavaScript. By no means am I saying that every site should use it.
My argument, as you mention in your last line, is that such a large percentage of users do have it enabled that JavaScript should not be seen as something that must be used as cautiously as people may seem.</description>
		<content:encoded><![CDATA[<p>I agree, Ryan, that corporate company websites don&#8217;t need JavaScript. By no means am I saying that every site should use it.<br />
My argument, as you mention in your last line, is that such a large percentage of users do have it enabled that JavaScript should not be seen as something that must be used as cautiously as people may seem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://wordsoftheweb.com/2009/12/javascript-is-now-standard/comment-page-1/#comment-73</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 02 Dec 2009 23:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://wordsoftheweb.com/?p=231#comment-73</guid>
		<description>Facebook is a bad example, very few website owners can or should compare themselves to a company/site like that simply because they&#039;re worlds apart.

Judgments on your site technology support should be made on an individual basis depending on the site and its visitors. If like me you work with very corporate companies where JS is all too likely to be disabled by a paranoid sys admins (and IE is used by 90%+ users… *sigh*) then it would be foolish not to make sure the site works with JS disabled. 

As I have already mentioned on Twatter as far as I&#039;m concerned Javascript should — in most cases — be used as a layer to enhance content, just like CSS. Relying on JS for vital elements of a site such as its content is to rely on yet another technology, another possible weak spot.

Of course if 98% of your visitors have JS enabled then go crazy all you like with it! :)</description>
		<content:encoded><![CDATA[<p>Facebook is a bad example, very few website owners can or should compare themselves to a company/site like that simply because they&#8217;re worlds apart.</p>
<p>Judgments on your site technology support should be made on an individual basis depending on the site and its visitors. If like me you work with very corporate companies where JS is all too likely to be disabled by a paranoid sys admins (and IE is used by 90%+ users… *sigh*) then it would be foolish not to make sure the site works with JS disabled. </p>
<p>As I have already mentioned on Twatter as far as I&#8217;m concerned Javascript should — in most cases — be used as a layer to enhance content, just like CSS. Relying on JS for vital elements of a site such as its content is to rely on yet another technology, another possible weak spot.</p>
<p>Of course if 98% of your visitors have JS enabled then go crazy all you like with it! <img src='http://wordsoftheweb.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
