Back in the days of MFC we built GUIs out of components - controls, panels, frames, dialogs, etc. Getting the faux-3D to line up was hard work but you could assemble complex UIs by wiring together simpler self-contained widgets. There was even a thriving commercial market for "exotic" components like trees and data tables.
Then the web happened and suddenly everything was a form. It was easy but it produced the kind of UIs that only the IRS could love. Pages were giant jumbled messes of template and jQuery. The best thing I can say about this era is that users had low expectations.
Thinking positively, frontend development means that if you hate the tools, all you have to do is wait two years. My Angular1 knowledge is past it's expiration date and ready to be tossed like sour milk -- which is an apt description of the taste it left in my mouth. So I'm not disappointed to be back at the bottom of the learning curve. Again.
author reviews each of the frameworks for each of the following application dev concepts
documentation
typescript support
build system
dependancy injection
component encapsulation
routing and fetching
ecosystem
conclusions - author chooses react.js -
ID: 5728
NAME: Opinionated-Comparison-of-React-Angular2-and-Aurelia
DESCRIPTION: [SUMMARY] Opinionated Comparison of React, Angular2, and Aurelia ] by Jeff
AUTHOR: article.author/s
EDITOR: article.editor/s
PUBLISHER: article.publisher/s
STATUS: Write
PRIORITY: -5
OWNER ID: 75