Introduction

Server side JavaScript has been around for a long time, and potentially offers some unique and interesting advantages over other languages because the same language is spoken by both client and server.

http://philip.greenspun.com/wtr/livewire.html

http://docs.sun.com/source/816-6411-10/contents.htm

Unfortunately, though, server side JavaScript is very fragmented. A script that accesses files can't be used without modification on both rhino and v8. Spidermonkey and JavaScriptCore can't both load in additional modules in the same way. A JavaScript web framework is very much tied to its interpreter and is often forced to create a bunch of APIs that Python, Ruby and Java programmers take for granted.

The goal for this project is to create a standard library that will ultimately allow web developers to choose among any number of web frameworks and tools and run that code on the platform that makes the most sense for their application.

This group/project was initially introduced in a blog posting: "What Server Side JavaScript Needs"

• Javascript @ "The Universal Design Pattern"
• Back to the Server: Server-Side JavaScript On The Rise
• The Next Big Language
• Revisiting serverside Javascript
• Server-side Javascript: Hope and opportunity
• A Future Web Development Framework App Logic