Sails

[Marcin Jekot]

Hello noders.

Has anyone used http://sailsjs.org/? I just watched their demo vid and it looks pretty sweet, can't believe I haven't seen it before.

[Marcin Jekot]

Okay, that video is over a year old, meaning archaic in the node eco system. (i.e. gulp has only just become cooler than grunt, but already brocolli is the new kid on the block).

Here I am now, a couple of google searches later, and about 35 browser tabs open, and my head is spinning :P I might have been happier ignorant, when I was just using express. I even thought I hit the jackpot with MEAN. But there seems to be a plethora of options out there, which is a good thing, but I guess I'm getting anxious just thinking about which ones to pick to evaluate, what if I miss that silver bullet ;-), as there is not time for them all, so I wanted to get an idea from you guys what you have used in the battle field, and what your experiences were.

For reference, this was the entry point: http://nodeframework.com/, and here is another list that seems pretty up to date as well: http://nodewebmodules.com/

[Adrian Rossouw]

On 11 May 2014, at 10:46 AM, Marcin Jekot <mar...@jekot.net> wrote:

Hello noders.

Has anyone used http://sailsjs.org/? I just watched their demo vid and it looks pretty sweet, can't believe I haven't seen it before.

I haven’t but I also don’t really like their approach to 

how things need to be provided by the framework. They are

still the first serious competitor to meteor.

I like derbyjs, even though they went for a rewrite at

just the wrong time. They did eventually give us sharejs,

which is a separate library that is much much more applicable

to any of the projects I have ever worked on, than either

meteor or sails.

—-

Adrian Rossouw. “Sensible Complexity”

- Full-Stack JavaScript Developer and Open Source Enthusiast

Portfolio | http://daemon.co.za/portfolio

Website   | http://daemon.co.za

Twitter   | @AdrianRossouw

GitHub    | Vertice

[Marcin Jekot]

I've known about derbyjs and meteor for quite some time now, but I guess in my mind they're still tagged as beta, not quite ready for the 'real stuff' yet. 

Do you think meteor is ready, and derby might be after the rewrite?

--
You received this message because you are subscribed to the Google Groups "Node Cape Town" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodecpt+u...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
Visit this group at http://groups.google.com/group/nodecpt.
For more options, visit https://groups.google.com/d/optout.

[Adrian Rossouw]

On 11 May 2014, at 9:24 PM, Marcin Jekot <mar...@jekot.net> wrote:

Do you think meteor is ready, and derby might be after the rewrite?

I think meteor makes assumptions that are not sensible for the

vast majority of applications, and has painted itself into a

corner in the way that it has built it’s community.

I think derby being ready is irrelevant as long as they build

high quality individual components that can be used to build

the right system for the problem at hand, rather than whatever

it is somebody else thinks you will need.

Many people have tried to be the rails-of-node, and

the community has mostly responded with ‘meh’.

[Connor Leech]

I've played a bit with sails and it's nice, it's opinionated with lots of structure. I switched back to using express because there's more documentation, more popular. If you're on the framework hunt also take a look at:

hapi: https://github.com/spumko/hapi

totaljs: http://www.totaljs.com/

expressio: built on top of express. easily integrate socket.io to existing applications https://github.com/techpines/express.io

and for comprehensive list you can dig http://nodeframework.com/

Good luck! interested to hear what you think using these ones