I think there would be a number of advantages to have a full-stack JavaScript stack:
- frontend guys could improve rendering and UX
- there are not so many Node/Full-Stack JavaScript apps out there that others could study
- the performance is just a lot better
- upgrades and maintenance are easier to do with npm I would say
Yes, just got the login/signup routes working. I guess I post here in some days when there is substantial progress. Will be interesting to see a full JavaScript stack for this forum.
Thanks! Good to hear it is working for you.
Yes, my thoughts on templating currently keep it simple from viewpoint of development, not so much for performance issues. But Node is much faster than Ruby too, and maybe someone is already working on a Viagra templating approach for Node :)
yes, for sure, that looks very interesting... I wonder if we could apply some of the ideas to rewrite EchoJS with NodeJS - I did a first start here: https://github.com/mulderp/echojs with a 1:1 translation for the Ruby source --- it's my first project with Express.js (used Restify before), but maybe you or others have some pointers how the views could be done?
thanks! this is still very experimental. But translating the Ruby source 1-1 so far went quite well. I am not yet so experienced with express.js. For example, maybe there are some other approaches to the templating. I am mainly experimenting with the Redis/Promisses setup.
Another interest for this would be adding a JS frontend (possibly Backbone driven). Also, it might be interesting to include an requireJS/Asset Pipeline approach.
if interested, we could have a small mailing list to dicuss a backend for EchoJS with Node: https://groups.google.com/forum/#!forum/echojs
Once this is setup, we could also try out something like rendr - shared rendering client/server
ok, this is what I had several weeks ago - https://github.com/mulderp/echojs - it needs some cleanup, but maybe useful already for someone getting an idea of how Lamernews could look like with a Node.js implementation