3 ms·

Just to get it out there, the current 800lb gorilla of Node.js webframeworks is Express: http://expressjs.com/guide.html http://expressjs.com/guide.html That

Just to get it out there, the current 800lb gorilla of Node.js webframeworks is Express: http://expressjs.com/guide.html 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 client and the server, live updating via Websockets as well as REST, views that can generate HTML on either end, with a built-in plan of attack for keeping common security holes in JS apps plugged.

CoffeeDregs 16y ago
J, Hadn't really noticed that feeling of not-quite-there-yet, but you summed up my feelings about node.js frameworks pretty well. (This is where someone tells me to start developing it myself...) I'll check into Express again and see if it's getting to the point where it's reasonable for a neophyte such as myself to invest in learning it and helping to develop it.
- percept 16y ago
  Also check out: https://github.com/tuxychandru/grasshopper https://github.com/tuxychandru/grasshopper
mathgladiator 16y ago
I'm working on some of that with my platform (which isn't done yet), but I'm pushing out a couple of products on it. https://github.com/mathgladiator/win https://github.com/mathgladiator/win
moe 16y ago
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.

CoffeeDregs 16y ago

J, Hadn't really noticed that feeling of not-quite-there-yet, but you summed up my feelings about node.js frameworks pretty well. (This is where someone tells me to start developing it myself...) I'll check into Express again and see if it's getting to the point where it's reasonable for a neophyte such as myself to invest in learning it and helping to develop it.

percept 16y ago
Also check out: https://github.com/tuxychandru/grasshopper https://github.com/tuxychandru/grasshopper

mathgladiator 16y ago

I'm working on some of that with my platform (which isn't done yet), but I'm pushing out a couple of products on it. https://github.com/mathgladiator/win https://github.com/mathgladiator/win

moe 16y ago

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.