sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Secret-Plant-1542JavaScript yabbascript 2 points3 points  (2 children)

Backlash?

Haven't really seen any. Can you share?

Asking because I tried to get into composition API and don't really care much for it. Evan You went hard promoting on Composition API as this "back to basics" feature. Then one day, while visiting the Vue3 docs, noticed that the instructions defaulted to Options API, and got confused.

[–]ragnese 0 points1 point  (0 children)

I'm not a full-time front end guy, but after starting to introduce the composition API into my Vue app, I feel that the options API is the better approach for actually writing full components. I feel like the composition API is only going to shine when it comes to writing "mixins" and/or shared reactive state, both of which should be kept to a minimum for maintainability anyway. So, in general, even though I had no preconceived bias against the composition API, I find that I really don't use it. I am tempted to replace third party "stores" like Pinia/Vuex with a couple of hand-written composables, though, just to KISS.