Frameworks come and go, if you don’t like it or don’t understand it, or don’t think it makes sense, well, because it kinda doesn’t make sense. Google created Angular but they don’t like it either, they trashed it and working on a new version. node.js creator doesn’t like node anymore, so he is now working on Deno. I can understand the pain when trying to learn bunch of npm or webpack, because they don’t have a good “user experience” even for programmers. We are at a transition time where people see web components benefits but there is no web standard support it, so people have to use these frameworks. But the web component standard is maturing itself nowadays. So the question- Is there a future for you? Totally, and on the contrary, I am not sure there is a future for these frameworks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Frameworks come and go, if you don’t like it or don’t understand it, or don’t think it makes sense, well, because it kinda doesn’t make sense. Google created Angular but they don’t like it either, they trashed it and working on a new version. node.js creator doesn’t like node anymore, so he is now working on Deno. I can understand the pain when trying to learn bunch of npm or webpack, because they don’t have a good “user experience” even for programmers. We are at a transition time where people see web components benefits but there is no web standard support it, so people have to use these frameworks. But the web component standard is maturing itself nowadays. So the question- Is there a future for you? Totally, and on the contrary, I am not sure there is a future for these frameworks.