<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Growing open web hackers from childhood</title>
	<atom:link href="http://frankhecker.com/2009/09/04/growing-open-web-hackers-from-childhood/feed/" rel="self" type="application/rss+xml" />
	<link>http://frankhecker.com/2009/09/04/growing-open-web-hackers-from-childhood/</link>
	<description>Trying to unite civility and truth in a few long blog posts</description>
	<lastBuildDate>Wed, 11 Jan 2012 13:03:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Richard Milewski</title>
		<link>http://frankhecker.com/2009/09/04/growing-open-web-hackers-from-childhood/#comment-1001</link>
		<dc:creator><![CDATA[Richard Milewski]]></dc:creator>
		<pubDate>Mon, 21 Sep 2009 18:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hecker.org/?p=1122#comment-1001</guid>
		<description><![CDATA[I share Atul&#039;s fond memories of those early machines.  BASIC was the second language I learned (after Fortran 2 on an IBM 7090 that I was never actually allowed to touch).  One of the keys to the success of machines like the Atari 400, the Commodore 64, and the AppleII was the approachability of the BASIC language for non programmers.  While even medium sized programs written in BASIC suffer from severe maintainability issues, the language does provide a low-friction introduction to programming.

I think it will take a focused effort to build a programming learning environment out of HTML, CSS, JavaScript and JQuery that is as approachable to newcomers as was BASIC.

There are two big obsticles.  First, JQuery depends upon the browser talking to a server, not just reading files from the file system of the local machine.  Some sort of bundled local web server with a one-click install would help.   But even then, getting from &quot;Hello World&quot; to a modest useful program in a client-server environment requires getting your head around scope and timing issues having to do with what&#039;s happening on the server and what&#039;s happening int he client side script.  These are not easy concepts for absolute beginners still struggling with simple control structures.  

The JavaScript security model is the second part of the problem.  Since it has no direct access to a file system on the local machine, it limits the range of tasks that can be undertaken without climbing up the client-server learning curve.  (Could a local web server be built as a JetPack?).

There are JavaScript implementations of languages such as TinyBASIC that might be part of the solution, but making the transition from a procedural BASIC approach to an object-oriented MVC paradigm isn&#039;t obvious either, so perhaps starting that way just teaches bad habits that would need to be unlearned.]]></description>
		<content:encoded><![CDATA[<p>I share Atul&#8217;s fond memories of those early machines.  BASIC was the second language I learned (after Fortran 2 on an IBM 7090 that I was never actually allowed to touch).  One of the keys to the success of machines like the Atari 400, the Commodore 64, and the AppleII was the approachability of the BASIC language for non programmers.  While even medium sized programs written in BASIC suffer from severe maintainability issues, the language does provide a low-friction introduction to programming.</p>
<p>I think it will take a focused effort to build a programming learning environment out of HTML, CSS, JavaScript and JQuery that is as approachable to newcomers as was BASIC.</p>
<p>There are two big obsticles.  First, JQuery depends upon the browser talking to a server, not just reading files from the file system of the local machine.  Some sort of bundled local web server with a one-click install would help.   But even then, getting from &#8220;Hello World&#8221; to a modest useful program in a client-server environment requires getting your head around scope and timing issues having to do with what&#8217;s happening on the server and what&#8217;s happening int he client side script.  These are not easy concepts for absolute beginners still struggling with simple control structures.  </p>
<p>The JavaScript security model is the second part of the problem.  Since it has no direct access to a file system on the local machine, it limits the range of tasks that can be undertaken without climbing up the client-server learning curve.  (Could a local web server be built as a JetPack?).</p>
<p>There are JavaScript implementations of languages such as TinyBASIC that might be part of the solution, but making the transition from a procedural BASIC approach to an object-oriented MVC paradigm isn&#8217;t obvious either, so perhaps starting that way just teaches bad habits that would need to be unlearned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lrbabe</title>
		<link>http://frankhecker.com/2009/09/04/growing-open-web-hackers-from-childhood/#comment-969</link>
		<dc:creator><![CDATA[lrbabe]]></dc:creator>
		<pubDate>Sat, 05 Sep 2009 20:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hecker.org/?p=1122#comment-969</guid>
		<description><![CDATA[&quot;what is the open web equivalent of that Atari 400 with BASIC that served as a first introduction to programming for Atul and others?&quot;

That is a really interesting question. The problem is that the Open Web is composed of three different technologies that are highly interdependent. 

There are probably two different approach to make the Web hackable and enjoyable by non-programmers:
- a high level approach which provides people with building blocks (widgets) to show what is possible to do ultimately with the Open Web, even though the control on those blocks and their interaction would be limited.
- a low level approach where people are taught the basics of the three technologies HTML, CSS and JavaScript. One would probably introduce jQuery in complement of JavaScript for its &quot;write less, do more&quot; philosophy and the clarity of its API compared to the DOM.

I&#039;m really looking forward to see Mozilla taking initiatives on that matter.

Louis-Rémi]]></description>
		<content:encoded><![CDATA[<p>&#8220;what is the open web equivalent of that Atari 400 with BASIC that served as a first introduction to programming for Atul and others?&#8221;</p>
<p>That is a really interesting question. The problem is that the Open Web is composed of three different technologies that are highly interdependent. </p>
<p>There are probably two different approach to make the Web hackable and enjoyable by non-programmers:<br />
- a high level approach which provides people with building blocks (widgets) to show what is possible to do ultimately with the Open Web, even though the control on those blocks and their interaction would be limited.<br />
- a low level approach where people are taught the basics of the three technologies HTML, CSS and JavaScript. One would probably introduce jQuery in complement of JavaScript for its &#8220;write less, do more&#8221; philosophy and the clarity of its API compared to the DOM.</p>
<p>I&#8217;m really looking forward to see Mozilla taking initiatives on that matter.</p>
<p>Louis-Rémi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Topher</title>
		<link>http://frankhecker.com/2009/09/04/growing-open-web-hackers-from-childhood/#comment-967</link>
		<dc:creator><![CDATA[Topher]]></dc:creator>
		<pubDate>Fri, 04 Sep 2009 22:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hecker.org/?p=1122#comment-967</guid>
		<description><![CDATA[I was just thinking about this the other day.  I have a 9 year old daughter who&#039;s starting to get interested in making the computer &quot;do things&quot;.  I&#039;m a web developer, and I was thinking of getting her into Javascript.  There&#039;s excellent instant feedback, and it&#039;s easy to make it do simple things and then grow from there.

Ironically, I still don&#039;t know it myself, I&#039;m more of a backend guy.  Maybe we could learn together.]]></description>
		<content:encoded><![CDATA[<p>I was just thinking about this the other day.  I have a 9 year old daughter who&#8217;s starting to get interested in making the computer &#8220;do things&#8221;.  I&#8217;m a web developer, and I was thinking of getting her into Javascript.  There&#8217;s excellent instant feedback, and it&#8217;s easy to make it do simple things and then grow from there.</p>
<p>Ironically, I still don&#8217;t know it myself, I&#8217;m more of a backend guy.  Maybe we could learn together.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

