In fact, many Vue projects are using composition Api in Vue2 via a plugin because it is so good.
I used Vue 2 for some projects a year or two ago, and recently have been comparing React hooks & Vue's composition API. Composition is definitely better than mixins, but as a new React user, hooks are feeling more intuitive right off the bat. With Vue 3, I feel like I have to decide for every component whether to stick with the options API or use the setup method, or end up with some awkward in-between.
I was always a big fan of Vue though; I'd appreciate any insight you can give on the Vue 3 additions.
I'm a fan of how Vue's composition API executes exactly once during a component lifetime (during `setup()`), whereas React hooks get set up again on every render. I find it I find Vue's approach easier to mentally model, and thus easier to write correct code (especially when doing something complicated where state changes / effect executions trigger each other). Since `setup()` is only run once, I can also do things like store non-reactive state in closure variables without wrapping those variables in hooks.
React hooks require manual dependency tracking and mistakes in this can lead hard to identify bugs
Vue has automatic dependency tracking, so that entire class of issues do not occur.
"It's not semantic"
They will stay or they will go but I think they are useful more than they are not but I don't think its the final form we'll all adopt.
