@Sam how would you compare sailsjs to loopback, because i agree with you, that the metrics i chose are lacking, but its also to so easy to compare...
2014-12-22 5:37 GMT+01:00 Sam Roberts <[email protected]>: > On Sun, Dec 21, 2014 at 7:07 PM, Alexander Praetorius <[email protected]> > wrote: > > sailsjs is backed by http://balderdash.co (it has ~4700 commits > > https://github.com/balderdashy/sails/ , last commit 6 hours ago) > > => first commit in january 2012 > > loopback is backed by http://strongloop.com (it has ~1300 commits > > https://github.com/strongloop/loopback/ , last commit 4 days ago) > > => first commit in april 2013 > > I don't think the stats above give a useful reflection of loopback > development, and from a quick look, not of sails, either. > > loopback is built in node style out of a number of components, mostly > optional, such as loopback DB connectors, core modules, swagger > support, yeoman tools for scaffolding and maintaining apps, etc. > Loopback is only the core, it changes not as fast the constellation > around it. > > From what I can see, sails is also composed of a set of modules, so > its activity is similarly not reflected by a single repo. > > As for the advice to use express because its simple... I would agree > its worth working through a few express tutorials to get a feel for > it, its the foundation of a number of other modules, including > loopback. > > That simplicity comes at quite a price, though - you have to > reimplement yourself a large set of features likely to be found in any > application, or worse, troll npmjs.org to try to figure out which of > the zillions of modules out there you should use to compose your app. > That latter is itself a significantly difficult thing to do for a > beginner to node. So using express for its simplicity just dumps you > fast into not so simple waters. > > One reason to consider a higher level framework such as loopback is > it works harder to cover a set of commonly required features (like an > ORM, completely absent from express), while at the same time giving > you the opportunity, once you've developed your own preferences, to > swap out components once you discover the areas where specialization > is truly important to you or your app. > > That's my two bits, > Sam > > -- > Job board: http://jobs.nodejs.org/ > New group rules: > https://gist.github.com/othiym23/9886289#file-moderation-policy-md > Old group rules: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nodejs/CACmrRmQXWeaZnpd5%3D1%2BXW7vthPMkS4SYd6Z2%3D%2BtbwG%2Bj55ZKuw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAN5%2BLUsUeYQPqekrif%2BvuU3GLwJJQXOG-0PwouMtB2dyco9ZbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
