On Mon, Dec 22, 2014 at 10:44 AM, Alexander Praetorius <[email protected]> wrote: > @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...
I would compare by features relevant to intended use. And I agree its easy, but it doesn't show anything useful. Is it that sails is more active? Is it that loopback is more stable? Maybe you are just seeing that they factor their code bases differently, which is profoundly uninteresting? The loopback GUI for scaffolding and run-time control, for example, last saw a commit 24 minutes ago, and its where most of the LB team has been pouring effort over the last month, leading to last weeks release of arc, something that sails probably doesn't have an equivalent of: http://strongloop.com/strongblog/arc-node-js-api-announcement/ If you don't want something like Arc, then it doesn't matter, of course. Remember the old stories of managers who rewarded devs by bugs-fixed? And how the bug-count went up, so they could get raises for fixing them? I'd hate to see a situation where developers attempted to split their commits into smaller and smaller changes to up their commit counts, to appear more productive and attract mind share :-(. 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/CACmrRmSXhRYLQ%2Ba%3DYatMRDkL7Lh7MyUdzgjuiMiF8w8x%2Bs8oUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
