Need advice about which tool to choose?Ask the StackShare community!

AngularJS

44.3K
32K
+ 1
5.2K
Symfony

5.5K
4.1K
+ 1
1.1K
Add tool

AngularJS vs Symfony: What are the differences?

Developers describe AngularJS as "Superheroic JavaScript MVW Framework". AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. On the other hand, Symfony is detailed as "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.

AngularJS can be classified as a tool in the "Javascript MVC Frameworks" category, while Symfony is grouped under "Frameworks (Full Stack)".

"Quick to develop", "Great mvc" and "Powerful" are the key factors why developers consider AngularJS; whereas "Open source", "Php" and "Community" are the primary reasons why Symfony is favored.

AngularJS and Symfony are both open source tools. It seems that AngularJS with 59.6K GitHub stars and 28.9K forks on GitHub has more adoption than Symfony with 21K GitHub stars and 6.98K GitHub forks.

According to the StackShare community, AngularJS has a broader approval, being mentioned in 2793 company stacks & 1806 developers stacks; compared to Symfony, which is listed in 355 company stacks and 267 developer stacks.

Advice on AngularJS and Symfony
Needs advice
on
Symfony
Node.js
and
Go

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.

See more
Replies (1)
Max Musing
Founder & CEO at BaseDash · | 6 upvotes · 48.4K views
Recommends
Node.js
at

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.

See more
Needs advice
on
Vue.js
React
and
AngularJS

What is the best MVC stack to build mobile-friendly, light-weight, and fast single-page application with Spring Boot as back-end (Java)? Is Bootstrap still required to front-end layer these days?

The idea is to host on-premise initially with the potential to move to the cloud. Which combo would have minimal developer ramp-up time and low long-term maintenance costs (BAU support)?

See more
Replies (3)
Carolyne Stopa
Full Stack Developer at Contabilizei · | 10 upvotes · 236.5K views
Recommends
Vue.js

React might be a good option if you're considering a mobile app for the future, because of react native. Although, Vue.js has the easiest learning curve and offers a better developer ramp-up time. Vue.js is great to build SPAs, very clean and organized and you won't have a lot of long-term maintenance problems (like AngularJS, for example). Bootstrap can still be used, but with flexbox there's no need anymore.

See more
Chaitanya Chunduri
Recommends
React

I recommend React because of less memory occupant compare to Angular, but this will depend on your organisation flexibility. When you use React you need to import different libraries as per your need. On the other side angular is a complete framework.

Performance-wise I vote for react js as it loads up quickly and lighter on the mobile. You can make good PWA with SSR as well.

See more
Recommends
React

If you are new to all three react will be a good choice considering, react-native will be useful if you want to build cross platform mobile application today or tomorrow. If you are talking about bootstrap styling framework than it's a choice you can style ur components by ur self or use bootstrap 4.0 framework. The complete stack mentioned above is platform agnostic u can run it anywhere you want be it cloud or on-premise.

See more
Decisions about AngularJS and Symfony
neha menahil

Have you ever stuck with the question that which one is the best front-end framework for you?

With continuous web development progress, the trends of the latest front-end technologies are also continuously changing with more and more sophisticated web features. These top front-end frameworks and libraries have made your complex web tasks more flexible and efficient.

Check out top front end frameworks and their features at https://www.nmtechedge.com/2020/09/24/top-4-trending-front-end-frameworks-2020/

See more
Peter Schmalfeldt
Senior Software Engineer · | 5 upvotes · 58.5K views

I honestly think the best choice for which framework you use should come down to your team's skills. If you have one Senior Dev that is great at React, but like 3-4 mid-level devs, and a handful of junior devs that know Vue.js ... maybe look at using Vue.js a little more seriously.

Yes, there are pros and cons to framework decisions, but I honestly see a LOT of teams not even consider whether a specific framework is a good fit.

See more
Peter Schmalfeldt
Senior Software Engineer · | 4 upvotes · 50.5K views

I honestly think the best choice for which framework you use should come down to your team's skills. If you have one Senior Dev that is great at React, but like 3-4 mid-level devs, and a handful of junior devs that know Angular ... maybe look at using Angular a little more seriously.

Yes, there are pros and cons to framework decisions, but I honestly see a LOT of teams not even consider whether a specific framework is a good fit.

See more
Kamaleshwar BN
Head of Engineering at Dibiz Pte. Ltd. · | 10 upvotes · 297.8K views

It was easier to find people who've worked on React than Vue. Angular did not have this problem, but seemed way too bloated compared to React. Angular also brings in restrictions working within their MVC framework. React on the other hand only handles the view/rendering part and rest of the control is left to the developers. React has a very active community, support and has lots of ready-to-use plugins/libraries available.

See more
José Oberto
Head of Engineering & Development at Chiper · | 14 upvotes · 263.6K views

It is a very versatile library that provides great development speed. Although, with a bad organization, maintaining projects can be a disaster. With a good architecture, this does not happen.

Angular is obviously powerful and robust. I do not rule it out for any future application, in fact with the arrival of micro frontends and cross-functional teams I think it could be useful. However, if I have to build a stack from scratch again, I'm left with react.

See more
John Clifford de Vera
Software Engineer at CircleYY · | 21 upvotes · 157.8K views

I used React not just because it is more popular than Angular. But the declarative and composition it gives out of the box is fascinating and React.js is just a very small UI library and you can build anything on top of it.

Composing components is the strongest asset of React for me as it can breakdown your application into smaller pieces which makes it easy to reuse and scale.

See more
Dennis Ziolkowski
CTO at Prepaid-Hoster · | 3 upvotes · 50K views
Migrated
from
AngularJS
to
Angular 2

I was first sceptical about using Angular over AngularJS. That's because AngularJS was so easy to integrate in existing websites. But building apps from scratch with Angular is so much easier. Of course, you have to build and boilerplate them first, but after that - you save a ton of time. Also it's very cozy to write code in TypeScript.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 732.9K views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • Vue Styleguidist as our style guide and pool of developed Vue.js components
  • Vuetify as Material Component Framework (for fast app development)
  • TypeScript as programming language
  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
  • ESLint, TSLint and Prettier for coding style and code analyzes
  • Jest as testing framework
  • Google Fonts and Font Awesome for typography and icon toolkit
  • NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
  • Large scaling. Vue.js can help to develop pretty large reusable templates.
  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
See more
Julius alvarado

It is a complete waste of time and life to learn a different framework to solve the same problem (Both AngularJS and Angular build A+ UI's, but both require a lot of time to learn). It's dumb to spend 200 hours learning AngularJS, then 200 hours learning Angular when you could spend 200 hours learning AngularJS and 200 hours learning how to solve a different problem (like AI/ML, Data Science, AR/VR, Digital Marketing, etc.)

See more
Jonas Stendahl

React has by far and away been our most important library choice throughout the history of Sellpy. It is a library that offers great flexibility supported by a really strong core. The React team is doing incredible work bringing quality features to the core project and tons of quality third party libraries fill in the gaps.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AngularJS
Pros of Symfony
  • 886
    Quick to develop
  • 586
    Great mvc
  • 570
    Powerful
  • 520
    Restful
  • 503
    Backed by google
  • 348
    Two-way data binding
  • 343
    Javascript
  • 327
    Open source
  • 305
    Dependency injection
  • 197
    Readable
  • 75
    Fast
  • 64
    Directives
  • 63
    Great community
  • 56
    Free
  • 38
    Extend html vocabulary
  • 29
    Components
  • 26
    Easy to test
  • 24
    Easy to learn
  • 23
    Easy to templates
  • 23
    Great documentation
  • 21
    Easy to start
  • 17
    Awesome
  • 17
    Light weight
  • 14
    Javascript mvw framework
  • 14
    Angular 2.0
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    Coffeescript
  • 8
    High performance
  • 7
    Mvc
  • 7
    Two-way binding
  • 7
    Lots of community modules
  • 6
    Clean and keeps code readable
  • 6
    Easy to e2e
  • 5
    Easy for small applications
  • 5
    One of the best frameworks
  • 4
    Works great with jquery
  • 4
    Fast development
  • 2
    I do not touch DOM
  • 2
    Community
  • 2
    The two-way Data Binding is awesome
  • 2
    Typescript
  • 2
    Dart
  • 2
    Hierarchical Data Structure
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 1
    Linear learning curve
  • 1
    Scopes
  • 1
    Programming fun again
  • 1
    Opinionated in the right areas
  • 1
    Fkin awesome
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Acoperișul
  • 1
    Great
  • 1
    Very very useful and fast framework for development
  • 1
    Amazing community support
  • 1
    Readable code
  • 1
    Common Place
  • 1
    Supports api , easy development
  • 0
    Js
  • 0
    Angular js
  • 0
    Bot Ionescu
  • 0
    Google.com
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Oautho loc
  • 0
    Shvzjn
  • 0
    Acoperișul 0757604335
  • 171
    Open source
  • 144
    Php
  • 125
    Dependency injection
  • 124
    Community
  • 117
    Professional
  • 76
    Doctrine
  • 69
    Organized
  • 64
    Modular architecture
  • 44
    Smart programming
  • 40
    Solid
  • 16
    Documentation
  • 13
    LTS releases
  • 8
    Robust
  • 8
    Easy to Learn
  • 7
    Good practices guideline
  • 7
    Bundle
  • 7
    Decoupled framework components
  • 6
    Service container
  • 6
    Simple
  • 4
    Powerful
  • 3
    Flexible

Sign up to add or upvote prosMake informed product decisions

Cons of AngularJS
Cons of Symfony
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn
  • 9
    Too many dependency
  • 7
    Lot of config files
  • 3
    YMAL
  • 2
    Feature creep
  • 1
    Bloated

Sign up to add or upvote consMake informed product decisions