Need advice about which tool to choose?Ask the StackShare community!
Ember.js vs Symfony: What are the differences?
What is Ember.js? 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.
What is Symfony? A PHP full-stack web framework. Symfony is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP. Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.
Ember.js and Symfony are primarily classified as "Javascript MVC Frameworks" and "Frameworks (Full Stack)" tools respectively.
"Elegant", "Quick to develop" and "Great mvc" are the key factors why developers consider Ember.js; whereas "Open source", "Php" and "Community" are the primary reasons why Symfony is favored.
Ember.js and Symfony are both open source tools. Symfony with 21.1K GitHub stars and 7.01K forks on GitHub appears to be more popular than Ember.js with 21.1K GitHub stars and 4.17K GitHub forks.
According to the StackShare community, Symfony has a broader approval, being mentioned in 375 company stacks & 278 developers stacks; compared to Ember.js, which is listed in 293 company stacks and 76 developer stacks.
I'm about to begin working on an API, for which I plan to add GraphQL connectivity for processing data. The data processed will mainly be audio files being downloaded/uploaded with some user messaging & authentication.
I don't mind the difficulty in any service since I've used C++ (for data structures & algorithms at least) and would also say I am patient and can learn fairly quickly. My main concerns would be their performance, libraries/community, and job marketability.
Why I'm stuck between these three...
Symfony: I've programmed in PHP for back-end in a previous internship and may do so again in a few months.
Node.js: It's newer than PHP, and it's JavaScript where my front-end stack will be React and (likely) React Native.
Go: It's newer than PHP, I've heard of its good performance, and it would be nice to learn a new (growing) language.
Go with Node.js. There's something really satisfying about being able to use a single language across your entire tech stack. Especially once you integrate GraphQL, which is effectively JSON.
Your second best option is Go, but the ecosystem around Node.js is quite a bit stronger. This will play a big factor when you start building functionality like file management, messaging (especially in real-time), and authentication. The libraries and documentation are just stronger for Node.
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 Symfony
- Open source177
- Php149
- Community130
- Dependency injection129
- Professional122
- Doctrine80
- Organized75
- Modular architecture71
- Smart programming47
- Solid45
- Documentation20
- LTS releases16
- Decoupled framework components10
- Robust10
- Easy to Learn10
- Good practices guideline8
- Service container8
- Bundle8
- Powerful7
- Simple7
- Flexible6
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 Symfony
- Too many dependency10
- Lot of config files8
- YMAL4
- Feature creep3
- Bloated1
Sign up to add or upvote consMake informed product decisions
What is Ember.js?
What is Symfony?
Need advice about which tool to choose?Ask the StackShare community!
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