Need advice about which tool to choose?Ask the StackShare community!
Ember.js vs Sails.js: What are the differences?
Developers describe Ember.js as "A JavaScript framework for creating ambitious web apps". Ember.js is a JavaScript framework that does all of the heavy lifting that you'd normally have to do by hand. There are tasks that are common to every web app; Ember.js does those things for you, so you can focus on building killer features and UI. On the other hand, Sails.js is detailed as "Realtime MVC Framework for Node.js". Sails is designed to mimic the MVC pattern of frameworks like Ruby on Rails, but with support for the requirements of modern apps: data-driven APIs with scalable, service-oriented architecture.
Ember.js belongs to "Javascript MVC Frameworks" category of the tech stack, while Sails.js can be primarily classified under "Microframeworks (Backend)".
"Elegant" is the top reason why over 121 developers like Ember.js, while over 41 developers mention "Data-driven apis " as the leading cause for choosing Sails.js.
Ember.js and Sails.js are both open source tools. Ember.js with 21.1K GitHub stars and 4.17K forks on GitHub appears to be more popular than Sails.js with 20.7K GitHub stars and 1.85K GitHub forks.
DigitalOcean, Twitch, and Square are some of the popular companies that use Ember.js, whereas Sails.js is used by Redox Engine, HYPH, and LapNghiep. Ember.js has a broader approval, being mentioned in 293 company stacks & 76 developers stacks; compared to Sails.js, which is listed in 32 company stacks and 13 developer stacks.
Pros of Ember.js
- Elegant126
- Quick to develop97
- Great mvc83
- Great community82
- Great router73
- Values conventions, there is one-true way to organize52
- Open source50
- Components44
- Mvc framework34
- Handlebars.js28
- Htmlbars13
- Yehuda katz11
- Tom dale10
- Great logo10
- It's NOT Google or Facebook6
- manages large data sets on the front end easily5
- Convention over Configuration5
- Glimmer: react-like rendering engine5
- Organized4
- Fast4
- Enterprise4
- Intelligent4
- It rocks4
- Good docs3
- Fastest spinning circles3
- IE8 support3
- Easy and Quick to develop2
- Documentation is finally active and updated2
- Flexibility1
- Business wins1
- Comprehensive1
- Great for big apps/many devs because its organized1
- Growing community1
- For building ambitious Web apps1
- Dependency Injection1
- Stability without stagnation1
Pros of Sails.js
- Data-driven apis49
- Waterline ORM47
- Mvc37
- Easy rest32
- Real-time25
- Open source21
- Service-oriented architecture19
- Scalable18
- Convension over configuration10
- Rails-like asset pipeline9
- Node machines and machinepacks9
- Easy route/controller generation7
- Ruby on Rails basic stuff for JS devs6
- CLI for scaffolding project pieces3
- WebSocket support3
- Supportive community1
Sign up to add or upvote prosMake informed product decisions
Cons of Ember.js
- Very little flexibility2
- Too much convention, too little configuration2
- Hard to integrate with Non Ruby apps1
- Hard to use if your API isn't RESTful1
Cons of Sails.js
- Waterline ORM5
- Defaults to VueJS4
- Standard MVC0
Sign up to add or upvote consMake informed product decisions
What is Ember.js?
What is Sails.js?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Sails.js?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12
+26
+26