Sails.js: Realtime MVC framework for Node.js
balderdashy.github.com
Sails.js: Realtime MVC framework for Node.js
1–10 of 107 posts
Re: Sails.js: Realtime MVC framework for Node.js
#2http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-...
Re: Sails.js: Realtime MVC framework for Node.js
#3Re: Sails.js: Realtime MVC framework for Node.js
#4After working with a few of these frameworks it always seems to lead to spaghetti code where the code I write weaves in and out of the framework at different pre-defined connection points (Sails calls them policies I think). I always take note of all the times the developer says 'automatically', these are all the places that will break when my requirements don't exactly match up with theirs.
Re: Sails.js: Realtime MVC framework for Node.js
#5Re: Sails.js: Realtime MVC framework for Node.js
#6This looks great! The automatic API generation is a killer feature that makes me want to try this out sometime soon. Only thing that seems strange to me is adding the /create, /update, and /destroy GET endpoints -- why not keep it RESTful?
Re: Sails.js: Realtime MVC framework for Node.js
#7This looks great! The automatic API generation is a killer feature that makes me want to try this out sometime soon. Only thing that seems strange to me is adding the /create, /update, and /destroy GET endpoints -- why not keep it RESTful?
I can see the desire to be able to execute non-GET commands via the browser's address bar. Another way Sails could accomplish that would be to accept "?method=PUT|POST|DELETE" to mimic the desired HTTP method.
Re: Sails.js: Realtime MVC framework for Node.js
#8I wish more people would read this blog post before writing another MVC framework in Node. http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-...
Re: Sails.js: Realtime MVC framework for Node.js
#9I wish more people would read this blog post before writing another MVC framework in Node. http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-...
The pace of invention today is based on iteration, building upon other successes and similar ideas - and its happening in real-time across a vast community. This is awesome.
Personally, I love that we have choices like derby, meteor and potentially, sail. Every effort has pro's / con's that may or may not be ideal for a particular use case. I would rather have more options than none.
Re: Sails.js: Realtime MVC framework for Node.js
#10Quick question: when demonstrating the socket.io piece, one aspect that differs with meteor is their ddp which only sends data diffs on a per client basis, not the entire subset as your demo showed. How are you planning to tackle that with any decent about of clients or data size?