Does anybody have experience with node frameworks? I\'ve been exploring
express.js, any other suggestions?
Yes, Node.js is trending at the moment. It has huge possibilities that developers can leverage to build highly robust and scalable web applications. So, it is worth a try before it is dead. After all, this is the world of web development!
Discussed here are the top 7 reasons why you should use Node.js
> Does anybody have experience with node frameworks? I\'ve been exploring
>> express.js, any other suggestions?
I\'ve used Express + Backbone to create a site alongside a number of
Express itself is a great, minimalistic tool. For authentication, look at
passport instead of everyauth.
The Flatiron set of tools are built to be a more modular swack at what
Express was created to solve.
I haven\'t built anything with Derby yet, but it looks like a good swipe at
creating a Rails-like, conventions-based framework for creating data-driven
web sites where the client UI can receive async updates from services
defined in the site.
When it comes down to deciding what to use, you\'ll find a *ton* more people
with Express experiences. I haven\'t really seen the pain points described
by the Nodejitsu guys as to why Flatiron is superior.
> We use Nodejs for nearly everything we do and it\'s fantastic. Express is
> great, but if you\'re just starting out you might want to also look at
> Meteor, which is a slightly more robust framework for apps that focuses on
> cool things like caching, latency compensation, and realtime.
> Have you built production software on Meteor? I looked at it when they launched and it seemed impressive but not fully baked. (For example: the data model is effectively a shared-memory scheme; there is no access control AFAIK).
I haven\'t worked with either, but it is worth checking out meteor.com and Derbyjs.com if you haven\'t already.
Founder, Right Buy
Tel: (650) 450-9301
On Apr 16, 2012, at 10:34 PM, rudy.wen wrote:
+1 for Express. I use it for all my startup weekend/hackathon projects. And
then Connect gives you a ton of great modular/customizable middleware
options as well.
On Tue, May 22, 2012 at 7:24 PM, mattwalters5 <mattwalte...@gmail.com>wrote:
We use Nodejs for nearly everything we do and it\'s fantastic. Express is great, but if you\'re just starting out you might want to also look at Meteor, which is a slightly more robust framework for apps that focuses on cool things like caching, latency compensation, and realtime.
Some of the various pieces we\'re using: Mongo, Nodejs, Express, Socket.io, Mongoose, and Jade for templates. Be happy to chat more about where we\'ve seen success and where we\'ve seen challenges. I would recommend it as a complete stack FWIW. For us, having one language between the client and the server is wonderful.
Also, +1 for Connect middleware.
On May 22, 2012, at 8:32 PM, Jimmy Jacobson wrote:
I can\'t speak to Meteor except to say I agree it looks like a work in
progress. Same with Derby, but my glance told me it seemed a little further
along (and with some better design decisions, IMO [modules available in
npm, angularjs style client side binding]).
Most people enforce their mongo schema using Mongoose (mongoosejs.com) or