Why Angular? Sergey Bielanovskiy
There is no “One size fits all" - not exists framework that will fit any situation - in this slides outlined subjective opinion about frontend framework selection that will fit next needs - should work fast on wide range of devices - should have strong architecture to force proper development and reduce cost of changes
A few words about competitors: React - React - simple enough solution with low learning curve - seems best fit for one-man or just little teams - probably can be built good enough solution with it, but it will have frontendish smell, not OOP, SOLID and so on
A few words about competitors: Vue.js - Vue.js - “fork” of angularJS (first version of Angular), first release 02.2014 - have very similar architecture to angular but more loose - again in pluses low learning curve but more robust solution than on React - team size 30 https://github.com/orgs/vuejs/people - supported by enthusiasts - sites that use https://madewithvuejs.com/ - Other - maybe exists other but this seems most prominent
A few words about competitors: Others - maybe exists other but this seems most prominent
Angular overview - Angular is rebuilt from ground up version of AngularJs, firstsecond release 09.2016 - current version is 6, and Google promise 2 versions per year - robust solution but with higher learning curver than competitors because of that - supported by ~60 team members - https://github.com/orgs/angular/people - supported by Google - https://www.madewithangular.com/
Speed - angular has modular system that allow loading only needed modules - at septemberoctober in plan release of angular 7 that besides others changes should bring new rendering engine that should increase speed - Ivy has been engineered with Tree shaking in mind, which means that application bundles will only include the parts of Angular source code that is actually used by the application.
Documentation - like Code Complete, it not just solve issues it enforce and suggest best software engineering practices - link with live examples where you can debug without spending time for setup locally anything
Top Notch SEO - really native seossr support done by guys that actually do the search
DI - inbuilt dependency injections system that helps code organization, and enforce speed
Two Way Data Binding - no code to populate input with data, just set this and model will be loaded to display and changed
Styles organization - have one global on app level and import it and separate on component level
Project folder structure example - https://medium.com/@motcowley/angular-folder-structure- d1809be95542 - great solution for really big projects
Architecture - live example:https://angular.io/generated/live-examples/toh-pt3/stackblitz.html - all decision is done, needed to force and follow, no discussions about this
Conclusion - for me this is no brainer that Angular is best frontend framework - it is fast - enforce best practices by design - no discussions about how and so just focus on implementation of the tasks, like with Symfony, in doubts link to doc

Why angular?

  • 1.
  • 2.
    There is no“One size fits all" - not exists framework that will fit any situation - in this slides outlined subjective opinion about frontend framework selection that will fit next needs - should work fast on wide range of devices - should have strong architecture to force proper development and reduce cost of changes
  • 3.
    A few wordsabout competitors: React - React - simple enough solution with low learning curve - seems best fit for one-man or just little teams - probably can be built good enough solution with it, but it will have frontendish smell, not OOP, SOLID and so on
  • 4.
    A few wordsabout competitors: Vue.js - Vue.js - “fork” of angularJS (first version of Angular), first release 02.2014 - have very similar architecture to angular but more loose - again in pluses low learning curve but more robust solution than on React - team size 30 https://github.com/orgs/vuejs/people - supported by enthusiasts - sites that use https://madewithvuejs.com/ - Other - maybe exists other but this seems most prominent
  • 5.
    A few wordsabout competitors: Others - maybe exists other but this seems most prominent
  • 6.
    Angular overview - Angularis rebuilt from ground up version of AngularJs, firstsecond release 09.2016 - current version is 6, and Google promise 2 versions per year - robust solution but with higher learning curver than competitors because of that - supported by ~60 team members - https://github.com/orgs/angular/people - supported by Google - https://www.madewithangular.com/
  • 7.
    Speed - angular hasmodular system that allow loading only needed modules - at septemberoctober in plan release of angular 7 that besides others changes should bring new rendering engine that should increase speed - Ivy has been engineered with Tree shaking in mind, which means that application bundles will only include the parts of Angular source code that is actually used by the application.
  • 8.
    Documentation - like CodeComplete, it not just solve issues it enforce and suggest best software engineering practices - link with live examples where you can debug without spending time for setup locally anything
  • 9.
    Top Notch SEO -really native seossr support done by guys that actually do the search
  • 10.
    DI - inbuilt dependencyinjections system that helps code organization, and enforce speed
  • 11.
    Two Way DataBinding - no code to populate input with data, just set this and model will be loaded to display and changed
  • 12.
    Styles organization - haveone global on app level and import it and separate on component level
  • 13.
    Project folder structure example -https://medium.com/@motcowley/angular-folder-structure- d1809be95542 - great solution for really big projects
  • 14.
    Architecture - live example:https://angular.io/generated/live-examples/toh-pt3/stackblitz.html -all decision is done, needed to force and follow, no discussions about this
  • 15.
    Conclusion - for methis is no brainer that Angular is best frontend framework - it is fast - enforce best practices by design - no discussions about how and so just focus on implementation of the tasks, like with Symfony, in doubts link to doc