@Shawn Lauriat: Thanks for the insightful response. Very helpful.
@David McCabe and @Jacob Rus: I agree with Shawn's statement that you can't write the entire application in JavaScript. You need to have server-side glue unless you want to expose all of your infrastructure (passwords, schemas) and code to the entire world. Many don't want to do that. A thick client approach would be to have the server respond to specific services requests, which isn't necessarily out of the question here.
@Jonathan Badeen: Jaxer looks suprisingly cool, but it requires you to write raw SQL strings right now until they decide on an API. The most important thing I want from a framework is object-relationship mapping.
by Scott Stevenson — Aug 02
@David McCabe and @Jacob Rus: I agree with Shawn's statement that you can't write the entire application in JavaScript. You need to have server-side glue unless you want to expose all of your infrastructure (passwords, schemas) and code to the entire world. Many don't want to do that. A thick client approach would be to have the server respond to specific services requests, which isn't necessarily out of the question here.
@Jonathan Badeen: Jaxer looks suprisingly cool, but it requires you to write raw SQL strings right now until they decide on an API. The most important thing I want from a framework is object-relationship mapping.