sails business case rev2.pptx ?
eh?
Sails.js: Realtime MVC framework for Node.js
61–70 of 107 posts
Re: Sails.js: Realtime MVC framework for Node.js
#62Earlier quoted context omitted.
Couldn't agree more. On a different topic, I've been toying with various JS MVC frameworks, but a lot of them tries to do their "magic" without actually explaining why the magic is necessary. These so called "conventions" at times hide way too many things, it actually makes it frustrating to understand. In the end, my choice came back to Backbone, which is the minimalistic framework. Having said that, I'm trying to p…
The argument (as I see it) against choosing something like Backbone in order to avoid framework "conventions" is that you inevitably end up inventing your own conventions to fill in the gaps. Fine if you're a one-man team (although still arguably only in the short-term), but if not, all you've done is shifted the "conventions" problem onto your co-workers, only now they have to learn yours , rather than the (hopefull…
Absolutely agree-- Backbone is a great step in the right direction, but it leaves tons of things to chance. We use Mast internally (https://github.com/balderdashy/mast) but I'm keeping a close eye on Ember and Angular. Also, if you're already doing Backbone, you might check out Marionette.
Re: Sails.js: Realtime MVC framework for Node.js
#63This 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://localhost:1337/user/1
# Create a new user http://localhost:1337/user/create?name=Fisslewick (or send an HTTP POST to http://localhost:1337/user)
# Update the name of the user with id 1 http://localhost:1337/user/update/1?name=Gordo (or send an HTTP PUT to http://localhost:1337/user/1)
# Destroy the user with id 1 http://localhost:1337/user/destroy/1 (or send an HTTP DELETE to http://localhost:1337/user/1)
Re: Sails.js: Realtime MVC framework for Node.js
#64Earlier quoted context omitted.
Node.js packages are usually small and self-contained. Without typing/APIs Node relies heavily on documentation, so packages which are not well-documented will fall into oblivion quickly. Who'd write a OSS library which nobody can use? My personal favorite, interactive docs! http://coffeescript.org/ I like these ones because of the straightforwardness: http://socket.io/ http://jade-lang.com/ http://mongoosejs.com/ An…
To be fair only one of these has a video
Well, not all projects show off on video. IMHO, a video is a sloooow way to present information. I'd rather skim through some examples/demos/interactive docs.
Re: Sails.js: Realtime MVC framework for Node.js
#65This 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?
If you're looking for a super simple solution, check out Sajak https://github.com/jed/sajak. It's great for making a basic JSON API.
Re: Sails.js: Realtime MVC framework for Node.js
#66Earlier quoted context omitted.
The argument (as I see it) against choosing something like Backbone in order to avoid framework "conventions" is that you inevitably end up inventing your own conventions to fill in the gaps. Fine if you're a one-man team (although still arguably only in the short-term), but if not, all you've done is shifted the "conventions" problem onto your co-workers, only now they have to learn yours , rather than the (hopefull…
Absolutely agree-- Backbone is a great step in the right direction, but it leaves tons of things to chance. We use Mast internally ( https://github.com/balderdashy/mast ) but I'm keeping a close eye on Ember and Angular. Also, if you're already doing Backbone, you might check out Marionette.
Mast looks cool! I'm going to check it out.
Re: Sails.js: Realtime MVC framework for Node.js
#67This 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…
Couldn't agree more. On a different topic, I've been toying with various JS MVC frameworks, but a lot of them tries to do their "magic" without actually explaining why the magic is necessary. These so called "conventions" at times hide way too many things, it actually makes it frustrating to understand. In the end, my choice came back to Backbone, which is the minimalistic framework. Having said that, I'm trying to p…
@sideproject Actually you can use Sails (https://github.com/balderdashy/sails) with whichever front-end framework you like. It's architected to serve a nice clean RESTful API and leave the front-end up to you.
Re: Sails.js: Realtime MVC framework for Node.js
#68I've looked the past week into sails.js. It brings a really cool new way to MVC Frameworks and makes it easy to do certain aspects. What I missed (and that's why I'm using express.js now) is the documentation (lacking) and testability (lacking as well). Also the ORM is really lacking. I'd recommend the authors to look into an existing ORM (sequelize or node-orm2) instead of creating an own one. Sails certainly needs…
Hi mweibel, I originally used Sequelize, but we wanted (a) noSQL support and (b) a bundled in-memory database. Waterline has very good test coverage, and it's professionally maintained by my Node.js studio, Balderdash. We invest heavily in its development, because it makes our client projects better and faster. Happy to answer any other questions about why we built our own ORM.
Ok I understand the decision now. Surely both (sequelize and node-orm2) aren't the one and only solution yet but I needed some stuff to be supported which you didn't (yet), e.g. indexes or something like that.
Did you have a look at jugglingdb? I don't use it also because of similar reasons why I didn't want waterline but basicly I think it's more mature than waterline is.
Re: Sails.js: Realtime MVC framework for Node.js
#69Any example applications made with Sails? A chat app?
Re: Sails.js: Realtime MVC framework for Node.js
#70This 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.
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.