<?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: What Server Side JavaScript needs</title>
	<atom:link href="http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/</link>
	<description>The Nuts and Bolts of Creating Great Software Products</description>
	<lastBuildDate>Sat, 23 Jan 2010 20:09:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: As Escolhas do MV (XVI) &#171; mvalente.eu/mv.*</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-211204</link>
		<dc:creator>As Escolhas do MV (XVI) &#171; mvalente.eu/mv.*</dc:creator>
		<pubDate>Sun, 17 Jan 2010 22:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-211204</guid>
		<description>[...] uso de Javascript no servidor atingiu massa critica e começou a ganhar forma. Sabe bem confirmar o que tinha previsto e fazer parte da [...]</description>
		<content:encoded><![CDATA[<p>[...] uso de Javascript no servidor atingiu massa critica e começou a ganhar forma. Sabe bem confirmar o que tinha previsto e fazer parte da [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Dangoor</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210871</link>
		<dc:creator>Kevin Dangoor</dc:creator>
		<pubDate>Thu, 08 Oct 2009 00:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210871</guid>
		<description>@jhuni: The effort that I introduced here has come a long way since this posting. More announcements are pending, but CommonJS has really covered quite a bit of ground and has several implementations (running on Rhino, SpiderMonkey, v8 and JavaScriptCore) that are tracking the standard-in-progress.</description>
		<content:encoded><![CDATA[<p>@jhuni: The effort that I introduced here has come a long way since this posting. More announcements are pending, but CommonJS has really covered quite a bit of ground and has several implementations (running on Rhino, SpiderMonkey, v8 and JavaScriptCore) that are tracking the standard-in-progress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jhuni</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210870</link>
		<dc:creator>jhuni</dc:creator>
		<pubDate>Wed, 07 Oct 2009 22:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210870</guid>
		<description>What you have talked about there is indeed one of the biggest problems with JavaScript. However, there are many other problems, for example the language itself is based upon an outdated model developed almost 12 years ago and the language itself has many flaws.

I also noticed you talked about the StandardLibrary there, indeed, Cross-Interpreter compatibility is probably the biggest issue with it, so on that note I implemented as much of the StandardLibrary as possible using JavaScript itself, that way a simple or old interpreter will have a minimum amount of problems.

http://openjsan.org/doc/j/jh/jhuni/StandardLibrary/1.81/index.html

On the issue of a standard repository, I do hope that JSAN is the answer to that problem. As for a &quot;standard way to include other modules&quot; me and others have been working hard on that and I do not think it is going to be resolved anytime soon. One of the biggest issues is how do you deal with HTTP requests?</description>
		<content:encoded><![CDATA[<p>What you have talked about there is indeed one of the biggest problems with JavaScript. However, there are many other problems, for example the language itself is based upon an outdated model developed almost 12 years ago and the language itself has many flaws.</p>
<p>I also noticed you talked about the StandardLibrary there, indeed, Cross-Interpreter compatibility is probably the biggest issue with it, so on that note I implemented as much of the StandardLibrary as possible using JavaScript itself, that way a simple or old interpreter will have a minimum amount of problems.</p>
<p><a href="http://openjsan.org/doc/j/jh/jhuni/StandardLibrary/1.81/index.html" rel="nofollow">http://openjsan.org/doc/j/jh/jhuni/StandardLibrary/1.81/index.html</a></p>
<p>On the issue of a standard repository, I do hope that JSAN is the answer to that problem. As for a &#8220;standard way to include other modules&#8221; me and others have been working hard on that and I do not think it is going to be resolved anytime soon. One of the biggest issues is how do you deal with HTTP requests?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Dangoor</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210685</link>
		<dc:creator>Kevin Dangoor</dc:creator>
		<pubDate>Tue, 25 Aug 2009 14:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210685</guid>
		<description>Right now, your best bet for server side JavaScript would be to use Narwhal on Rhino, because you&#039;ll get the easiest database support:

http://narwhaljs.org

Vision Web Hosting appears to be an inexpensive hosting choice for Java:

http://www.visionwebhosting.net/?a_aid=0eb3aaa3</description>
		<content:encoded><![CDATA[<p>Right now, your best bet for server side JavaScript would be to use Narwhal on Rhino, because you&#8217;ll get the easiest database support:</p>
<p><a href="http://narwhaljs.org" rel="nofollow">http://narwhaljs.org</a></p>
<p>Vision Web Hosting appears to be an inexpensive hosting choice for Java:</p>
<p><a href="http://www.visionwebhosting.net/?a_aid=0eb3aaa3" rel="nofollow">http://www.visionwebhosting.net/?a_aid=0eb3aaa3</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CB Gayles</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210684</link>
		<dc:creator>CB Gayles</dc:creator>
		<pubDate>Tue, 25 Aug 2009 02:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210684</guid>
		<description>Dear Sir:

I am looking for a web host that supports server side javascript.
I program in client side javascript &amp; html. I need to use server side
language so that I can access a data base. 

I hope that you can recommend one/several.

Please respond at your earliest convenience.

Thank you,
CB.Gayles</description>
		<content:encoded><![CDATA[<p>Dear Sir:</p>
<p>I am looking for a web host that supports server side javascript.<br />
I program in client side javascript &amp; html. I need to use server side<br />
language so that I can access a data base. </p>
<p>I hope that you can recommend one/several.</p>
<p>Please respond at your earliest convenience.</p>
<p>Thank you,<br />
CB.Gayles</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bespin to Helma &#171; Gozilla planet</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210478</link>
		<dc:creator>Bespin to Helma &#171; Gozilla planet</dc:creator>
		<pubDate>Tue, 21 Apr 2009 16:58:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210478</guid>
		<description>[...] to Kevin Dangoor who pushed ServerJS group, cause it seems that soon we&#8217;ll be able to write a webapp for helma [...]</description>
		<content:encoded><![CDATA[<p>[...] to Kevin Dangoor who pushed ServerJS group, cause it seems that soon we&#8217;ll be able to write a webapp for helma [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blue Sky On Mars &#187; ServerJS: one week into building a better JavaScript</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210309</link>
		<dc:creator>Blue Sky On Mars &#187; ServerJS: one week into building a better JavaScript</dc:creator>
		<pubDate>Thu, 05 Feb 2009 14:08:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210309</guid>
		<description>[...] actually been 8 days now since I introduced the ServerJS group. As Peter Michaux mentions in &#8220;A Bright Future for Standardized [...]</description>
		<content:encoded><![CDATA[<p>[...] actually been 8 days now since I introduced the ServerJS group. As Peter Michaux mentions in &#8220;A Bright Future for Standardized [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael O'Brien</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210296</link>
		<dc:creator>Michael O'Brien</dc:creator>
		<pubDate>Fri, 30 Jan 2009 19:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210296</guid>
		<description>You describe the needs very well.

Ejscript is early (0.9.X) but it has many of the features you are describing. It is currently stand-alone as an interpreter, but an apache module is almost complete.

It implements Javascript plus a well defined module scheme and extensive library with SQLite, ORM, File I/O, Sockets, HTTP, E4X/XML and other APIs in the library. It also has a Rails like web framework. 

It is early, but moving fast and will transition to 1.0 sometime late this quarter.</description>
		<content:encoded><![CDATA[<p>You describe the needs very well.</p>
<p>Ejscript is early (0.9.X) but it has many of the features you are describing. It is currently stand-alone as an interpreter, but an apache module is almost complete.</p>
<p>It implements Javascript plus a well defined module scheme and extensive library with SQLite, ORM, File I/O, Sockets, HTTP, E4X/XML and other APIs in the library. It also has a Rails like web framework. </p>
<p>It is early, but moving fast and will transition to 1.0 sometime late this quarter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hannesw</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210294</link>
		<dc:creator>hannesw</dc:creator>
		<pubDate>Fri, 30 Jan 2009 09:49:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210294</guid>
		<description>You have a good point here. Helma has always benefited from the huge quantity of java libraries out there, which can be use quite comfortably and naturally through Rhino&#039;s LiveConnect. I still see that as a major advantage of any Java based JS engine over those written in C or C++ on the server side.

Of course, the problem with JavaScript is that it was _conceived_ as an embedded language, and that any features that would have allowed for a &#039;ecosystem&#039; to grow around it (such as module support) were ommitted deliberately. While this is a great feature for some (see &lt;a href=&quot;http://log.ometer.com/2008-08.html&quot; rel=&quot;nofollow&quot;&gt;Havoc Pennington&#039;s blog entry&lt;/a&gt;, for instance), it&#039;s a real problem for JavaScript as a fully grown language. 

In &lt;a href=&quot;http://github.com/hns/helma-ng/tree/master&quot; rel=&quot;nofollow&quot;&gt;Helma NG&lt;/a&gt; I implemented a module system that gives each module its own scope, and it really opens the language up.</description>
		<content:encoded><![CDATA[<p>You have a good point here. Helma has always benefited from the huge quantity of java libraries out there, which can be use quite comfortably and naturally through Rhino&#8217;s LiveConnect. I still see that as a major advantage of any Java based JS engine over those written in C or C++ on the server side.</p>
<p>Of course, the problem with JavaScript is that it was _conceived_ as an embedded language, and that any features that would have allowed for a &#8216;ecosystem&#8217; to grow around it (such as module support) were ommitted deliberately. While this is a great feature for some (see <a href="http://log.ometer.com/2008-08.html" rel="nofollow">Havoc Pennington&#8217;s blog entry</a>, for instance), it&#8217;s a real problem for JavaScript as a fully grown language. </p>
<p>In <a href="http://github.com/hns/helma-ng/tree/master" rel="nofollow">Helma NG</a> I implemented a module system that gives each module its own scope, and it really opens the language up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: This is a test. This is only a test &#124; Delusions of Grandeur</title>
		<link>http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/comment-page-1/#comment-210291</link>
		<dc:creator>This is a test. This is only a test &#124; Delusions of Grandeur</dc:creator>
		<pubDate>Thu, 29 Jan 2009 21:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.blueskyonmars.com/2009/01/29/what-server-side-javascript-needs/#comment-210291</guid>
		<description>[...] Blue Sky On Mars » What Server Side JavaScript needs  Rate this: 3.2 Sphere: Related Content    &#171; A Flick of the Wrist [...]</description>
		<content:encoded><![CDATA[<p>[...] Blue Sky On Mars » What Server Side JavaScript needs  Rate this: 3.2 Sphere: Related Content    &laquo; A Flick of the Wrist [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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