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

71–80 of 107 posts

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

#71

Post by awj »

rane wrote: post #27
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

In my mind "I need to turn to my version control system to have a clue what just happened" is a great example of having too much magic for a production product.

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

#73

Post by dimadima »

this looks cool; thanks for posting.

i just wish the hero graphic wasn't so gross. what we have there is a white man-child in the middle, spectacled, with little beady eyes behind the big frames, hunched forward like he wants to get punched in the face. to his right we have a hot a chick, her sexy little stomach is showing. she's got big anime eyes. i'm not sure what her deal is—is she the project manager? to the left is a black dude smiling so wide you can't even see his face. that guy looks straight out of some racist shit from the 20s. i wouldn't be surprised if it turned out that guy was a white dude in blackface. anyway, weird graphic.

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

#76

Post by adamauckland »

api wrote: post #49

Node is excellent from an architectural point of view, but I can't get over JavaScript. I really think web developers have Stockholm syndrome with this language.

Doing simple JavaScript is easy. Doing JavaScript well, that scales and doesn't become a spaghetti mess is _hard_.

Having said that, there are a tonne of libraries and tools which make it much better these days. A language is only as good as the available libraries and there are some really good ones on npm.

What, particulary, do you find problematic?

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

#77

Post by smrtinsert »

mikermcneil wrote: post #63
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?

Hey Peter-- RESTful endpoints are supported. The other options are just there for convenience while testing. You can disable those routes later if you like in your routing table. Policy mapping happens at a controller level to solve this very problem and prevent devs from inadvertently granting access to a piece of code they didn't mean to. # List of all users http://localhost:1337/user # Find the user with id 1 http…

how would you delete the incorrectly created key from the video?

nice work btw, the end to end of it is attractive if somewhat magical.

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

#78

Post by tonyblundell »

NikolaTesla wrote: post #70
tonyblundell wrote: post #28

Earlier quoted context omitted.

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

Definitely not promoting it! That's a convenience feature to make it easy to see what's happening during development. You can disable that behavior in your routing table.

If it's on the homepage and in the docs, people will copy it without questioning it. That's why people use frameworks.

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

#79

Post by smrtinsert »

api wrote: post #49

Node is excellent from an architectural point of view, but I can't get over JavaScript. I really think web developers have Stockholm syndrome with this language.

JavaScript is a powerful seductress, I've fallen for her many times. I remember writing a js web server and web application framework when rhino came out. It was an awesome thing at first since I could turn tons of java code into one liners easily, but as my app grew over the several thousand line mark it became more of a hassle to find and remember the apis i was creating in this white fire of code genesis. Finally I started getting angry everytime I had to lookup my new methods for stuff and I said f this, tooling > *. My pace went to zero as code size increased, but with Java if anything it increases or at the very least stays constant. JS is great for my personal site and small projects, but if someone gave me 1 million and said build an app that you can iterate on that would be potentially huge for purpose X, I would use java.

Still though, I stare longingly into JS's eyes when she looks my way...

Post reply on HN