Talk:Server-side JavaScript

message: The list contains a lot of projects that have been abandoned or discontinued. (like Rhinola, last (alpha/beta) release in 2005)
Further, it would be useful to sort the entries into categories. It's doesn't make much sense to put something like jsext in the same list as Myna olr Helma.
84.63.153.144 (talk) 14:37, 12 July 2009 (UTC)
thread_title: Purging and Sorting the List

message: Shouldn't Jaxer - http://www.aptana.com/jaxer - be on the list?  —Preceding unsigned comment added by 80.229.216.136 (talk) 12:48, 26 January 2008 (UTC)
thread_title: Jaxer?

message: Shouldn't NodeJS - http://nodejs.org/ - be on the list?   —Preceding unsigned comment added by 130.133.8.114 (talk) 08:16, 9 February 2011 (UTC)
thread_title: nodejs?

message: How can it be here when it`s no released yet. Probably not exists at all.  —Preceding unsigned comment added by 213.208.179.221 (talk) 16:00, 26 February 2010 (UTC)
thread_title: Wakanda?

message: I found this table both useful and poorly laid out when I was trying to find out about client-side JavaScript for a new project I wanted to try. For a start, most of the links listed are basically small research projects that were of no use to me. It wasn't til I tried the last (and 22nd!!) link, Jaxer, that I found a genuinely popular and supported implementation of the concept (honorable mention to Appjet, also good but more a webapp host than a cross-platform client-side JS implementation).
I feel certain that this area would be better suited as a worded article than a table. The table could perhaps be moved to a List of Server-side JavaScript implementations page. Instead this article could have paragraphs about the difference between client-side and server-side JS, the history and present of server-side JS, popular implementaions and uses, those kinds of things.
In the mean time I'm going to move the Jaxer and Junction listings from the tail end of the table as the rest seem to be in alphabetical order. --Pipedreambomb (talk) 23:53, 31 March 2008 (UTC)
thread_title:  Table not a useful way to present this data 

message: There was a very brief time during the development of .Net in 2000 when Microsoft started publishing code samples for ASP written in JScript as a distinct preference ! "In line with future developments of the Microsoft Scripting platform". Not much trace left - might be able to find some in archive.org ? 
Google ["script language JSCRIPT runat server" site:microsoft.com] finds ~1,300 instances of <script language="JScript" runat=server>
--87.194.174.252 (talk) 11:52, 19 March 2009 (UTC)
thread_title:  Microsoft preferred SSJS in 2000 

message: Introducing JScript .NET - notable ?
--87.194.174.252 (talk) 11:52, 19 March 2009 (UTC)
thread_title:  JScript .NET 

message: The title is confusing. Should be "list of javascript server-side frameworks" or "solutions" or something as that.
The real article should explains what is ssj. 
Macaldo (talk) 08:59, 10 October 2009 (UTC)
thread_title: Confusing title

message: Seeing as I have yet to see compelling evidence that Jaxer is to be considered 'dead,' I will remove that wording for now. Ironmagma (talk) 06:48, 3 July 2010 (UTC)
thread_title:  Jaxer "dead" 

message: The first two links both lead to nihonsoft.org, which appears to be dead to me. I've tried checking it on isup.me and that agrees.  — Preceding unsigned comment added by 87.194.161.82 (talk) 11:35, 22 June 2011 (UTC)
thread_title:  Dead Links Under Specification