For further actions, you may consider blocking this person and/or reporting abuse
Read next
Effective Logging and Monitoring for Node.js Applications
Sushant Gaurav -
Building a Smooth, Keyboard-Aware Component in React Native
Ajmal Hasan -
Introduction to Jest: Unit Testing, Mocking, and Asynchronous Code
Dimitris Stoikidis -
How to use Cookie Consent in a React App with react-cookie-consent
Muchhal Sagar -
Top comments (11)
No no, go directly for the bleeding edge stuff always. Unless you work on an "enterprise" setting. ;)
All the documentation and core concepts are well explained in Vue2 and how you work with it is not that different. The differences are that Vue2 is enhanced under the hood and a few extra funcionalities that comes handy.
No. You can skip vue 1
I haven't been keeping up with vue but I think as with everything, if the latest version is stable and therefore the community has no reason not to use it, then learn the latest version.
Though I can't say I am really experienced in many frameworks, I would guess that learning what you might need to know if you ever work with earlier versions is going to be easy.
No, I started with Vue 2 and I love it :D
No, but you should be aware of the differences so that when you run across examples that use parts of Vue 1 that are no longer in Vue 2 ($broadcast and $dispatch for example) you'll know to avoid them or adapt them.
Go directly to Vue 2
NO
Nope
I think you should learn vue.js 2. Because vue developers always will talk about vue 2. which means all new modules will create vue 2 (maybe. I thought)