91–100 of 107 posts
Earlier quoted context omitted.
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.
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…
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?
Judging from the description it does what the other 1000+ Node MVC frameworks do. What's the advantage of Sails over them? CRUD scaffolding is nothing new in Node's ecosystem. Apparently their edge is that users can manipulate the database on their own in the default scaffold? EDIT: Downvote without a comment is not constructive. This is a legitimate question. Care to explain?
I'm guessing the downvotes are for the snideness of your remark. A more respectable way to phrase your question would've been to simply ask how this framework compares to some of the other well known Node frameworks and why might I look into Sails to solve a specific problem instead of some of the others that are available.
I'll try throwing random smileys next time :P
The whole point of Node/npm/Express (as a popular module) is its modularity. Node is not just about JS on the server, it reflects a paradigm shift -- a movement away from too much abstraction and magic back to lean and simple systems. And it's unbelievable fast. Sorry to say but such frameworks and ideas are from the last decade (Rails was the main reason why I switched to Node).
This is something that I spend a lot of time thinking about (for instance, how can we apply this to the organization of corporations?)..
Earlier quoted context omitted.
$ 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.
Earlier quoted context omitted.
If it's on the homepage and in the docs, people will copy it without questioning it. That's why people use frameworks.
Not you though, sounds like!
But seriously, I'm new to Node. If I see examples of bad practice on the home page, I've no way of knowing if the framework is going to be teaching me more bad practices in the areas I'm not familiar with yet.
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.
Any example applications made with Sails? A chat app?