Live data from Hacker News

Ask HN: Best server-side Javascript framework

news.ycombinator.com

21–23 of 23 posts

Re: Ask HN: Best server-side Javascript framework

#21
post #9

What don't you like about Ringo's programming model? I've found the community to be very helpful, despite it's relatively small size.

Fair point. Clearly, I don't have enough experience with it to gripe about specifics, but it seemed more like a web programming library than like a Rails-ish web framework. I'm a huge fan of convention over configuration and RingoJS seemed more configuration-y. ...but the point of this "Ask HN" was to set aside my preconceptions and to get people's thoughts on what's happening in the JS Server Side world, so I'll go look at RingoJS with fresh eyes.

Re: Ask HN: Best server-side Javascript framework

#22

Just to get it out there, the current 800lb gorilla of Node.js webframeworks is Express: http://expressjs.com/guide.html That said, I think we're all still waiting for the real JS Application framework to appear. For better or for worse, Express is more or less a Sinatra clone for static pages. I'm hoping to see a true end-to-end JS system emerge sometime in 2011: one that provides models that can run on both the cli…

waiting for the real JS Application framework to appear

Yes, please! This area is so ripe, it hurts.

Backbone.js (or similar) screams to grow into a client/server hybrid that could finally turn web development into what it should be - after all those years.

As a datapoint, I'm currently fleshing out a rails hack to auto-generate javascript form-validation code from the rails model validations. The impedance mismatch is nasty, to say the least.

And this is just a tiny fragment of the pains that would evaporate when we finally get to treat server and client as two sides of the same coin.

Re: Ask HN: Best server-side Javascript framework

#23
post #20
post #18

Earlier quoted context omitted.

RingoJS is not slow . We use it in the Erbix backend, running a separate Rhino/RingoJS engine for each account. It's really stable, fast, multi-threaded. We use it in conjunction with PostgreSQL JDBC driver, serving large source code files, rendering templates written in JavaScript, static files upload/download, etc. http://www.erbix.com is an Erbix app running on a standard Erbix account.

If you are running Apache Tomcat (or anything based on Coyote), as I can see from headers, you are _already_ serving slower than Node. Just because Tomcat needs more time to parse and return the response than Node. Only Jetty with NIO connector has comparably high speed. (Yes, I've tested by myself). And, JFYI, you have to move static content to nginx or lighthttpd, Coyote serves static files even worse than Apache w…

Why this obsession with app container performance?

It does not matter either way in practice. People are running large websites on ruby, remember?

Post reply on HN