[Satam]

Yeah, I don't get it. I used Vue because it was straightforward. The options interface was Vue. Now, if it keeps getting more complicated and also has two ways to go about things, and the docs are split into two as well... Why not just go for React that's complicated and more popular?

[sampullman]

I thought the composition API was clunky at first and resisted migrating for a few minor versions, but it's matured nicely. I find it much simpler than the options API, and migration was much easier than I expected.

I don't see it as two ways in practice, just the legacy way for old projects (which still has good support), and the newer/better way.

[rty32]

What's the biggest Vue.js project you worked on?

Asking because my experience is that as soon as you have a large and complex component that needs to have multiple, mostly independent functionalities, you'll find the composition APIs to be a godsend. Not to mention all the IDE support. You won't see that until you have first have experience with it.

[Semaphor]

I find the composition API to be clearer and simpler in almost every way. Script setup is amazing.

Also proper typescript support without annoying workarounds, that alone would make it worth it.

[conradfr]

Typescript works fine with the option api.

[sensanaty]

`PropType` would beg to differ.

the `defineProps` macro is much, much better than the old way of declaring prop types, for one.