adding some updates to the sails comparison

Author: ekryski

getting-started/readme.md

@@ -29,7 +29,7 @@ Out of the box Feathers provides a lot of what you need to build a modern app. A
 - **Logging** - Feathers comes with a very simplistic logger that has sane defaults for production. However, it is easily swappable to allow you to customize to your needs.
 
 ### First Class Websockets
-Most real-time frameworks only emit messages over websockets. You interact with your server over REST and then receive events over websockets. Feathers allows you to **send** and **receive** data over websockets, so you could even remove REST altogether and simply use websockets to communicate with your app.
+Most real-time frameworks only clients to **receive** messages over websockets. You interact with your server over REST and then receive events over websockets. Feathers allows you to **send** and **receive** data over websockets, so you could even remove REST altogether and simply use websockets to communicate with your app.
 
 ## Built on the Shoulders of Giants
 Because we utilize some already proven modules, we spend less time re-inventing the wheel, are able to move incredibly fast, and have small well-tested, stable modules.

getting-started/vs/sails.md

@@ -1,5 +1,13 @@
 # Feathers vs. Sails
 
-From a feature standpoint Feathers and Sails are probably the closest. Both provide real-time REST API's, multiple db support, and are client agnostic. Both frameworks also use Express, but Feathers supports Express 4, while Sails only supports Express 3.
+From a feature standpoint Feathers and Sails are probably the closest. Both provide real-time REST API's, multiple db support, and are client agnostic but Feathers can be used on the client as well as the server. Both frameworks also use Express, but Feathers supports Express 4, while Sails only supports Express 3.
 
-Even though the features are very similar, Feathers achieves this with MUCH less code, which means less stuff to break and maintain making it easy to continuously upgrade to the latest version of Express. We also don't assume how you want to manage your assets by letting you use your build tool of choice. Feathers provides lightweight services and hooks instead of a full-blown ORM, and we let you write code instead of long config files to define relationships and security policies.
+Both Feathers and Meteor are real-time JavaScript platforms that provide front end and back end support. However, in addition to allowing clients to subscribe to events, Feathers allows clients to push data to the server over websockets. Meteor only allows clients to receive messages over websockets.
+
+Sails follows the MVC pattern whereas Feathers provides lightweight services to define your resources. We use hooks to define your business logic including validations, security policies and serialization in reusable, chainable modules, instead of configuration files.
+
+Feathers supports multiple ORMs while Sails only supports their Waterline ORM.
+
+Just like Meteor, Sails allows you to receive messages via websockets on the client but does not support the client sending messages to the server over websockets.
+
+Even though the features are very similar, Feathers achieves this with much less code. We also don't assume how you want to manage your assets by letting you use your build tool of choice and scale by easily splitting into services as opposed to spinning up multiple monolithic apps (which you can also do with Feathers if you want).