2 ms·
Most likely due to vue 2 to 3 transition. Vue 3 introduced many improvements and breaking changes. This also made many libraries lose compatibility with Vue 3.
by rk06 5y ago
Most likely due to vue 2 to 3 transition. Vue 3 introduced many improvements and breaking changes. This also made many libraries lose compatibility with Vue 3. Not a good thing.
While vue 3 was soft launched a year ago. The transition is still happening. With Vue 3 becoming default last week(feb 7). And major vue frameworks (vuetify and nuxt) just still working to support vue 3.
I expect satisfaction to increase next year, when ecosystem catches up. And dissatisfied folks switch to other options.
One thing to note is v2.7 is still shrouded darkness. Now, that major vue 3 work is done, Clarity and good support on v2.7 will also improve satisfaction.
- samwillis 5y agoVue 3 is Vues "Python 3" moment, give it a couple of years and it will be mostly forgotten. Just as Python changed its string type to Unicode breaking compatibility, Vue changed the reactivity system. The other changes in Vue3 wouldn't fundamentally break compatibility on their own but made sense to fold into a big overhaul, just as Python did with various other changes in v3.