Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sails.js: Realtime MVC framework for Node.js

balderdashy.github.com

Post reply on HN
Print view View original

21–30 of 107 posts

Re: Sails.js: Realtime MVC framework for Node.js

#22

Post by cvrajeesh »

jonny_eh wrote: post #6
peter_l_downs wrote: post #3

This 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.

According to HTTP - GET request should be idempotent. Even if you mimic the other verbs using query string, it is still a GET request.

Re: Sails.js: Realtime MVC framework for Node.js

#24

Post by j_col »

mweibel wrote: post #23
j_col wrote: post #21

Please stop calling anything on the internet real-time. Response time is not guaranteed here.

I guess you mean hard realtime. What usually on the web is called realtime is soft realtime IMHO.

Sure I get, but I think it just dilutes the meaning of the term "real-time" to use it in a soft context.

Re: Sails.js: Realtime MVC framework for Node.js

#26

Post by tracker1 »

gregr401 wrote: post #9
trungonnews wrote: post #2

I 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-...

Except without leveraging those V8 features, we don't have what makes node. 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…

I think my issues with this are that it's cool, but there's no example of security, and the tests are pretty much missing... I tend to look for either tests, or samples for how things get done, and without any security/authentication bits, I don't know what I would use something like this for.

Re: Sails.js: Realtime MVC framework for Node.js

#27

Post by rane »

bunkat wrote: post #4

This looks incredibly cool, but if there is one thing that I've learned, it's that less magic is generally better when building a real production application (vs a weekend project). While typing something like 'sails generate model User' is nice, I literally have no idea what that just did. In the video it then shows a user creating new attributes on the model via a REST API - what??(he even mistakenly adds a bad att…

  $ sails generate model User
  $ git diff

Re: Sails.js: Realtime MVC framework for Node.js

#28

Post by tonyblundell »

peter_l_downs wrote: post #3

This 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?

It does look exciting, but I can't trust a framework that promotes saving data on a GET request.

Re: Sails.js: Realtime MVC framework for Node.js

#29

Post by widblom »

bunkat wrote: post #4

This looks incredibly cool, but if there is one thing that I've learned, it's that less magic is generally better when building a real production application (vs a weekend project). While typing something like 'sails generate model User' is nice, I literally have no idea what that just did. In the video it then shows a user creating new attributes on the model via a REST API - what??(he even mistakenly adds a bad att…

Agreed.

Re: Sails.js: Realtime MVC framework for Node.js

#30

Post by marcamillion »

kaoD wrote: post #19
marcamillion wrote: post #12

I love how this is put together and packaged. The graphics, nice intro video, and very clear docs. Well done! I wish more OSS projects would put more care in their docs. Adding more personality and character and just cleaning it up - making it feel more approachable.

This is pretty standard presentation for Node.js packages.

Oh really? As a non-Node.js guy, I would love to see some others. Can you show me some examples please?

Thanks!

Post reply on HN