<?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: Douglas Crockford on Web Standards and JavaScript</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 18:10:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: pd</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-812666</link>
		<dc:creator>pd</dc:creator>
		<pubDate>Tue, 21 Oct 2008 01:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-812666</guid>
		<description>I could not agree more that the standards development process is a failure.

Why don&#039;t those responsible for standards take a tip from the industry they operate in - software development - and release smaller, more concisely defined, standards as &#039;point releases&#039;. 

The one thing the web is currently crying out for is better form controls. Look at all the JS libraries trying to hack controls like sliders, drag and drop, file upload, the list is long! These should be provided natively by the browser. 

It is comical to babble on about the web as a developer platform that can compete with the desktop until these controls are mature and ubiquitous. 

Unfortunately attempts to implement such simple improvements to the web get gobbled up by glitzy crap like SVG, Canvas (two drawing APIs for the web when arguably we don&#039;t need one (yet)!) etc.

Xforms? Web Forms 2? Irrelevant! Get the damn controls in the browser! NOW! 

When standards development is too slow, cut the crap and innovate!</description>
		<content:encoded><![CDATA[<p>I could not agree more that the standards development process is a failure.</p>
<p>Why don&#8217;t those responsible for standards take a tip from the industry they operate in &#8211; software development &#8211; and release smaller, more concisely defined, standards as &#8216;point releases&#8217;. </p>
<p>The one thing the web is currently crying out for is better form controls. Look at all the JS libraries trying to hack controls like sliders, drag and drop, file upload, the list is long! These should be provided natively by the browser. </p>
<p>It is comical to babble on about the web as a developer platform that can compete with the desktop until these controls are mature and ubiquitous. </p>
<p>Unfortunately attempts to implement such simple improvements to the web get gobbled up by glitzy crap like SVG, Canvas (two drawing APIs for the web when arguably we don&#8217;t need one (yet)!) etc.</p>
<p>Xforms? Web Forms 2? Irrelevant! Get the damn controls in the browser! NOW! </p>
<p>When standards development is too slow, cut the crap and innovate!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: blacklight</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-810111</link>
		<dc:creator>blacklight</dc:creator>
		<pubDate>Thu, 16 Oct 2008 04:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-810111</guid>
		<description>One of the strengths of javascript is the way it can be functional (think c) and object oriented (c++) at the same time.  It also treats every object and its members as a key/value associative array (think hash or map).

A good example of that is this &lt;a href=&#039;http://zedwood.com/article/104/javascript_-_drag_and_drop_dialog_box&#039; rel=&quot;nofollow&quot;&gt;Drag and Drop DHTML Dialog&lt;/a&gt;.  Its pretty cool.  It is a total crowse-browser compatible drag and drop interface.  An example is given with a simple dialog box.  But it is written in object oriented javascript, which makes easy to reuse (namespace collisions etc).</description>
		<content:encoded><![CDATA[<p>One of the strengths of javascript is the way it can be functional (think c) and object oriented (c++) at the same time.  It also treats every object and its members as a key/value associative array (think hash or map).</p>
<p>A good example of that is this <a href='http://zedwood.com/article/104/javascript_-_drag_and_drop_dialog_box' rel="nofollow">Drag and Drop DHTML Dialog</a>.  Its pretty cool.  It is a total crowse-browser compatible drag and drop interface.  An example is given with a simple dialog box.  But it is written in object oriented javascript, which makes easy to reuse (namespace collisions etc).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: veronicay</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-806344</link>
		<dc:creator>veronicay</dc:creator>
		<pubDate>Thu, 09 Oct 2008 11:43:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-806344</guid>
		<description>Thanks Caligula -- I freely admit I haven&#039;t spent a lot of time really getting to understand JS, but then my point was that 2 days isn&#039;t enough :-) Even leaving aside browser problems I have just never got comfortable with it. I know I should look more closely at some of the popular libraries that make life a lot easier -- I&#039;ve dabbled with Prototype but only enough to accomplish a few specific tasks.

So why wouldn&#039;t you choose it as a first language? :-)</description>
		<content:encoded><![CDATA[<p>Thanks Caligula &#8212; I freely admit I haven&#8217;t spent a lot of time really getting to understand JS, but then my point was that 2 days isn&#8217;t enough :-) Even leaving aside browser problems I have just never got comfortable with it. I know I should look more closely at some of the popular libraries that make life a lot easier &#8212; I&#8217;ve dabbled with Prototype but only enough to accomplish a few specific tasks.</p>
<p>So why wouldn&#8217;t you choose it as a first language? :-)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Caligula</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-806011</link>
		<dc:creator>Caligula</dc:creator>
		<pubDate>Wed, 08 Oct 2008 22:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-806011</guid>
		<description>@veronicay: JavaScript-the-language is cross-browser enough that you can accomplish quite a lot of education. Browser incompatibilities rear their head when dealing directly w/ a few DOM issues.

Throwing a reasonable JavaScript library removes that issue, and can be a good way to introduce some of the more advanced capabilities at the same time.

It&#039;s not the language *I&#039;d* choose as a first language, but browser incompatibility wouldn&#039;t be the reason why.</description>
		<content:encoded><![CDATA[<p>@veronicay: JavaScript-the-language is cross-browser enough that you can accomplish quite a lot of education. Browser incompatibilities rear their head when dealing directly w/ a few DOM issues.</p>
<p>Throwing a reasonable JavaScript library removes that issue, and can be a good way to introduce some of the more advanced capabilities at the same time.</p>
<p>It&#8217;s not the language *I&#8217;d* choose as a first language, but browser incompatibility wouldn&#8217;t be the reason why.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: veronicay</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-805609</link>
		<dc:creator>veronicay</dc:creator>
		<pubDate>Wed, 08 Oct 2008 08:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-805609</guid>
		<description>&lt;blockquote&gt;I wondered, would we be able to preserve that low barrier to entry that makes JavaScript something you can pick up as your first language and feel confident after just a day or two?&lt;/blockquote&gt;

I find this statement a little hard to swallow :-) I teach online courses for novice programmers and I would say that client-side Javascript is a really bad language to start with. Admittedly it&#039;s C-style syntax, which will come in useful later, but the big problem IMHO is browser incompatibilities; you can get it working in Firefox for example, and then discover it&#039;s broken in IE, or vice versa. This is very dispiriting for newbies. Many students give up in despair, because they can&#039;t understand it -- when they would have had a much easier time with PHP, for example.

&quot;Comfortable in a day or two&quot;? I&#039;ve been programming for 20 years and I&#039;m still not comfortable with Javascript -- though admittedly I haven&#039;t tried very hard ;-) I&#039;ll be happy if someone can convince me otherwise!</description>
		<content:encoded><![CDATA[<blockquote><p>I wondered, would we be able to preserve that low barrier to entry that makes JavaScript something you can pick up as your first language and feel confident after just a day or two?</p></blockquote>
<p>I find this statement a little hard to swallow :-) I teach online courses for novice programmers and I would say that client-side Javascript is a really bad language to start with. Admittedly it&#8217;s C-style syntax, which will come in useful later, but the big problem IMHO is browser incompatibilities; you can get it working in Firefox for example, and then discover it&#8217;s broken in IE, or vice versa. This is very dispiriting for newbies. Many students give up in despair, because they can&#8217;t understand it &#8212; when they would have had a much easier time with PHP, for example.</p>
<p>&#8220;Comfortable in a day or two&#8221;? I&#8217;ve been programming for 20 years and I&#8217;m still not comfortable with Javascript &#8212; though admittedly I haven&#8217;t tried very hard ;-) I&#8217;ll be happy if someone can convince me otherwise!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Zagar</title>
		<link>http://www.sitepoint.com/blogs/2008/10/07/douglas-crockford-on-web-standards-and-javascript/comment-page-1/#comment-805100</link>
		<dc:creator>Randy Zagar</dc:creator>
		<pubDate>Tue, 07 Oct 2008 17:29:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=3064#comment-805100</guid>
		<description>I fail to see how web standards can &quot;lead innovation on the Web&quot;.  Standards are created after you figure out how to reliably do a new thing.  Since doing a new thing is &quot;innovation&quot;, trying to make standards &quot;lead innovation&quot; is very much putting the cart before the horse.</description>
		<content:encoded><![CDATA[<p>I fail to see how web standards can &#8220;lead innovation on the Web&#8221;.  Standards are created after you figure out how to reliably do a new thing.  Since doing a new thing is &#8220;innovation&#8221;, trying to make standards &#8220;lead innovation&#8221; is very much putting the cart before the horse.</p>]]></content:encoded>
	</item>
</channel>
</rss>
