Stefan Nieuwenhuis
1 min readAug 8, 2018

--

It’s unclear to me if you’re referring to AngularJS (as in v1) or Angular (v2+). I think that the future for the first is rather grim. It has served it’s cause, but has too many flaws to succeed in today’s world of modern JavaScript frameworks. Angular (v2+), on the contrary, has, in my eyes, a very bright future.

But frameworks will be frameworks and will probably be replaced by new solutions to (not yet) existing problems in the future. The risk of having to switch to another framework and leave a codebase full of unusable legacy code is imminent and always there.

That’s why I love another approach: Framework independent component libraries. Here are three reasons why.

--

--

Stefan Nieuwenhuis
Stefan Nieuwenhuis

Written by Stefan Nieuwenhuis

Stefan Nieuwenhuis is software engineer, loves to play sports, read books and occasionally jump out of planes (with a parachute that is).

No responses yet