<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Javascript will be the Next Big Language</title>
	<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/</link>
	<description>Utterly random, incoherent and disjointed rants and ramblings...</description>
	<pubDate>Tue, 07 Oct 2008 02:07:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Terminally Incoherent &#187; Blog Archive &#187; Stages in Life of a Web Developer</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-10025</link>
		<pubDate>Mon, 01 Sep 2008 20:51:47 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-10025</guid>
					<description>[...] Personally I think Javascript has a bright future. It&#8217;s just that a lot of people are still stuck at Stage 1 and the stigma of toy language keeps them there indefinitely. Stage 2 is transitory and brief, and almost always results in a transition to Stage 3. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Personally I think Javascript has a bright future. It&#8217;s just that a lot of people are still stuck at Stage 1 and the stigma of toy language keeps them there indefinitely. Stage 2 is transitory and brief, and almost always results in a transition to Stage 3. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke Maciak</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8921</link>
		<pubDate>Wed, 30 Apr 2008 01:54:04 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8921</guid>
					<description>Good point Derrick! It should be up there on my list, but I totally missed it. Thanks for bringing this up.</description>
		<content:encoded><![CDATA[<p>Good point Derrick! It should be up there on my list, but I totally missed it. Thanks for bringing this up.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Derrick</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8920</link>
		<pubDate>Wed, 30 Apr 2008 00:55:12 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8920</guid>
					<description>I'm surprised you didn't mention tamarin "a high-performance, open source implementation of the ECMAScript 4th edition (ES4) language specification." http://www.mozilla.org/projects/tamarin/ .  

It's basically the next rhino .

It's used by flash player, as you've sort of already mentioned for the AVM2 (ActionScript VM2).  

ActionScript 3 is basically the closest thing to JavaScript 2.0 right now.</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised you didn&#8217;t mention tamarin &#8220;a high-performance, open source implementation of the ECMAScript 4th edition (ES4) language specification.&#8221; <a href="http://www.mozilla.org/projects/tamarin/" rel="nofollow">http://www.mozilla.org/projects/tamarin/</a> .  </p>
<p>It&#8217;s basically the next rhino .</p>
<p>It&#8217;s used by flash player, as you&#8217;ve sort of already mentioned for the AVM2 (ActionScript VM2).  </p>
<p>ActionScript 3 is basically the closest thing to JavaScript 2.0 right now.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke Maciak</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8918</link>
		<pubDate>Wed, 30 Apr 2008 00:26:39 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8918</guid>
					<description>[quote comment="8916"]You bet. Look at http://www.effectgenerator.com for an example.

You forgot that Flash is now written in Javascript, which is pretty important![/quote]

Wow, that is pretty impressive. :)</description>
		<content:encoded><![CDATA[<p><span style="padding-left: 10px;"><strong>Ed</strong> said:</span></p>
<blockquote cite="http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8916"><p>
You bet. Look at <a href="http://www.effectgenerator.com" rel="nofollow">http://www.effectgenerator.com</a> for an example.</p>
<p>You forgot that Flash is now written in Javascript, which is pretty important!</p>
</blockquote>
<p>Wow, that is pretty impressive. <img src="http://www.terminally-incoherent.com/blog/wp-includes/images/smilies/icon_smile.gif" alt=")" class="wp-smiley" />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ed</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8916</link>
		<pubDate>Tue, 29 Apr 2008 21:03:31 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8916</guid>
					<description>You bet. Look at http://www.effectgenerator.com for an example.

You forgot that Flash is now written in Javascript, which is pretty important!</description>
		<content:encoded><![CDATA[<p>You bet. Look at <a href="http://www.effectgenerator.com" rel="nofollow">http://www.effectgenerator.com</a> for an example.</p>
<p>You forgot that Flash is now written in Javascript, which is pretty important!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mike</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8910</link>
		<pubDate>Tue, 29 Apr 2008 12:08:24 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8910</guid>
					<description>JavaScript continues to blow my mind every day - it's like play-dough for the web.  Server-side JavaScript?  That's a frightening thought that I'm now going to have to look into deeper - thanks for the article!</description>
		<content:encoded><![CDATA[<p>JavaScript continues to blow my mind every day - it&#8217;s like play-dough for the web.  Server-side JavaScript?  That&#8217;s a frightening thought that I&#8217;m now going to have to look into deeper - thanks for the article!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: davey</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8897</link>
		<pubDate>Sat, 26 Apr 2008 20:13:53 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8897</guid>
					<description>Just in case you haven't noticed, Javascript is already the most deployed language there is. pretty much every web request is from a device supporting js, (braindead mobile stuff aside), no other language has the reach of js. 

The amount of developers that are familiar with it way exceeds even java,  this is why js as an end to end platform facility it is a very compelling argument. (developers, developers, developers...)

but to get there lots of stuff needs to be happen. libs, performance etc. It is happening though, client js, server js, couchDB, is the most coherent stack available today, a stack where you can learn a single language to it's fullest and use that knowledge in whatever part of the app you are working on.

I'm hopeful it will work out, but so many factors are in play that you can't make a rational prediction of the outcome.

If nothing else fun times ahead.</description>
		<content:encoded><![CDATA[<p>Just in case you haven&#8217;t noticed, Javascript is already the most deployed language there is. pretty much every web request is from a device supporting js, (braindead mobile stuff aside), no other language has the reach of js. </p>
<p>The amount of developers that are familiar with it way exceeds even java,  this is why js as an end to end platform facility it is a very compelling argument. (developers, developers, developers&#8230;)</p>
<p>but to get there lots of stuff needs to be happen. libs, performance etc. It is happening though, client js, server js, couchDB, is the most coherent stack available today, a stack where you can learn a single language to it&#8217;s fullest and use that knowledge in whatever part of the app you are working on.</p>
<p>I&#8217;m hopeful it will work out, but so many factors are in play that you can&#8217;t make a rational prediction of the outcome.</p>
<p>If nothing else fun times ahead.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Binny V A</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8891</link>
		<pubDate>Fri, 25 Apr 2008 18:14:07 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8891</guid>
					<description>JavaScript rules in the browser scripting area - it is already the 'big language' there. 

But will it get a hold in the other fields(Server side programming, shell scripting, etc)? &lt;a href="http://www.openjs.com/articles/javascript_scripting_language.php" rel="nofollow"&gt;I hope it will&lt;/a&gt; - but I am not very optimistic about it.</description>
		<content:encoded><![CDATA[<p>JavaScript rules in the browser scripting area - it is already the &#8216;big language&#8217; there. </p>
<p>But will it get a hold in the other fields(Server side programming, shell scripting, etc)? <a href="http://www.openjs.com/articles/javascript_scripting_language.php" rel="nofollow">I hope it will</a> - but I am not very optimistic about it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luke Maciak</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8888</link>
		<pubDate>Fri, 25 Apr 2008 04:26:38 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8888</guid>
					<description>[quote post="2406"]Static typing has 2 benefits: Speed, Speed.

I don’t buy the “early error detection” security that some people try to sell. Asserts and test suite are the right way to manage software code quality.[/quote]

Well said. Still, sometimes sacrificing some speed for increased readability, and expressibility of your code is not that bad.

This argument is a little bit like the argument about garbage collection. Any language that uses it, pays a performance penalty but most people (sans die hard C zealots) agree that it is a good thing in most circumstances.

When we are talking about web applications, the overhead of dynamically typed language is negligible if you consider the real bottlenecks such as database queries and other remote calls.

[quote post="2406"]Also HaXe is a very cool project but not a good choice for anyone looking for the future development language, you may be able to compile down HaXe code to other things but you are always limited to what that language can do, programming in HaXe is just confusing and disconnected. But still cool.[/quote]

Until today I never heard about HaXe. It's a coll idea, but I don't really buy into the whole meta-language thing. It seems like an unnecessary layer of abstraction if you ask me - and a potentially leaky one. I have to take a closer look at it to see if my gut feeling is right though. It might be halfway decent after all.</description>
		<content:encoded><![CDATA[<blockquote cite="http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/"><p>
Static typing has 2 benefits: Speed, Speed.</p>
<p>I don’t buy the “early error detection” security that some people try to sell. Asserts and test suite are the right way to manage software code quality.</p>
</blockquote>
<p>Well said. Still, sometimes sacrificing some speed for increased readability, and expressibility of your code is not that bad.</p>
<p>This argument is a little bit like the argument about garbage collection. Any language that uses it, pays a performance penalty but most people (sans die hard C zealots) agree that it is a good thing in most circumstances.</p>
<p>When we are talking about web applications, the overhead of dynamically typed language is negligible if you consider the real bottlenecks such as database queries and other remote calls.</p>
<blockquote cite="http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/"><p>
Also HaXe is a very cool project but not a good choice for anyone looking for the future development language, you may be able to compile down HaXe code to other things but you are always limited to what that language can do, programming in HaXe is just confusing and disconnected. But still cool.</p>
</blockquote>
<p>Until today I never heard about HaXe. It&#8217;s a coll idea, but I don&#8217;t really buy into the whole meta-language thing. It seems like an unnecessary layer of abstraction if you ask me - and a potentially leaky one. I have to take a closer look at it to see if my gut feeling is right though. It might be halfway decent after all.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tyler Larson</title>
		<link>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8886</link>
		<pubDate>Thu, 24 Apr 2008 21:22:30 +0000</pubDate>
		<guid>http://www.terminally-incoherent.com/blog/2008/04/23/javascript-will-be-the-next-big-language/#comment-8886</guid>
					<description>JavaScript in its current form has major problems but the next version is shaping up to be something much different. It will be years before we can really use it in a browser but it will be very close to what ActionScript 3 is now. 

The best thing that JavaScript2 has going for it is that there is a large community of people including all of the major companies figuring it all out as a group now rather then what is happening with Ruby were everything is being broken up because of different ideas. (CRuby, JRuby, IronRuby, Rubinius, and I think there is another one ) JavaScript should have a common base for all platforms as soon as they figure it all out. 

Also HaXe is a very cool project but not a good choice for anyone looking for the future development language, you may be able to compile down HaXe code to other things but you are always limited to what that language can do, programming in HaXe is just confusing and disconnected. But still cool.</description>
		<content:encoded><![CDATA[<p>JavaScript in its current form has major problems but the next version is shaping up to be something much different. It will be years before we can really use it in a browser but it will be very close to what ActionScript 3 is now. </p>
<p>The best thing that JavaScript2 has going for it is that there is a large community of people including all of the major companies figuring it all out as a group now rather then what is happening with Ruby were everything is being broken up because of different ideas. (CRuby, JRuby, IronRuby, Rubinius, and I think there is another one ) JavaScript should have a common base for all platforms as soon as they figure it all out. </p>
<p>Also HaXe is a very cool project but not a good choice for anyone looking for the future development language, you may be able to compile down HaXe code to other things but you are always limited to what that language can do, programming in HaXe is just confusing and disconnected. But still cool.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.261 seconds -->
