The new composition syntax is miscalculated move from the Vue team, and with a change like this the past in most cases tell a story of the future. Just like React and Angular, the community will be split or forced to run with this new trendy syntax. The core values of Vue are now depreciated.
In my opinion, Vue Composition API is a blessing for experienced developer that has more opinionated codebase and needs to abstract and compose the functionality, with proper typings. But, it's also not necessary for simple use-case of Vue component.
The concern that I can see is that, any new libraries or tutorial will move towards composition API, which splits the gap further with the common Vue interface.
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.
The new composition syntax is miscalculated move from the Vue team, and with a change like this the past in most cases tell a story of the future. Just like React and Angular, the community will be split or forced to run with this new trendy syntax. The core values of Vue are now depreciated.
I may understand your concern.
In my opinion, Vue Composition API is a blessing for experienced developer that has more opinionated codebase and needs to abstract and compose the functionality, with proper typings. But, it's also not necessary for simple use-case of Vue component.
The concern that I can see is that, any new libraries or tutorial will move towards composition API, which splits the gap further with the common Vue interface.