4 ms·
I would suggest using Vue.js[1]. It's the most popular library following React[2] and one of the strong original pioneers in the field. One of the strongest si
by Etheryte 8y ago
I would suggest using Vue.js[1]. It's the most popular library following React[2] and one of the strong original pioneers in the field.
One of the strongest sides of Vue is that it's opinionated and very easy to get started with; if you've used React before you'll feel right at home. While the library obviously keeps evolving over time, most of the knowledge applicable from version 1 from years ago is still relevant today — the core API is very stable.
Most of all, however, I would like to highlight that keeping up to the bleeding edge of any ecosystem in the modern frontend world will be a pain. You don't have to use the latest release of everything, use a good stable build and you'll run into a lot less headaches.
[1] https://vuejs.org/ https://vuejs.org/
[2] https://2018.stateofjs.com/front-end-frameworks/overview/ https://2018.stateofjs.com/front-end-frameworks/overview/
- csdreamer7 8y agoI like your post. Been considering Vue for a while. > You don't have to use the latest release of everything, use a good stable build and you'll run into a lot less headaches. In the above case, there was a security vulnerability with React with the older version that still worked with v2 of the firebase library. I asked this question because I wasn't happy seeing React just make breaking changes and cut support off like that.
- acemarke 8y agoWhat "security vulnerability" are you talking about? None of React's recent releases have had anything to do with security vulnerabilities. And, as I described in my other comment, the changes were in React-Redux, not React, and the changes that broke other libraries were not considered part of our public API.
- Juliennng 8y agoReact is very stable, component back before react use class still works today (before 2016). I consider that's a pretty stable core API.