Re:The end of Framework Churn
by joshiefishbein on Monday September 18, 2017 @04:07PM
(#15279069)
Web components don't take care of the full ecosystem that is the front-end and will prove irrelevant to framework churn.
If anything, web components make framework hopping marginally easier resulting in a more likely (marginally) exodus of a framework when something new and shiny comes by.
Front-end framework churn is ultimately a result of the ever-growing Javascript community and its relatively fast-paced development. Because we now treat the front-end as seriously (and formally) as we treat the back-end and server/service stack, we will see the constant invention/innovation/adoption cycle that we see in these aspects of technology.
Framework churn is here to stay until browsers change the way the front-end works altogether.
If anything, web components make framework hopping marginally easier resulting in a more likely (marginally) exodus of a framework when something new and shiny comes by.
Front-end framework churn is ultimately a result of the ever-growing Javascript community and its relatively fast-paced development. Because we now treat the front-end as seriously (and formally) as we treat the back-end and server/service stack, we will see the constant invention/innovation/adoption cycle that we see in these aspects of technology.
Framework churn is here to stay until browsers change the way the front-end works altogether.