The composition API is opt-in, but will likely be the de facto standard if/when the majority of projects and tutorials use it.

> will likely be the de facto standard if/when the majority of projects and tutorials use it.

Why would you think that? To me it sounds like a completely unbased opinion and goes agains everything that I read in the v3 documentation or in numerous discussions.

> Possibly the biggest change is our new Composition API, which is entirely additive- the previous Options API will continue to be supported, as the Composition API is an advanced feature.

https://v3.vuejs.org/guide/migration/introduction.html

The Composition API is the last item in the API reference, the Options API is positioned much more prominently.

https://v3.vuejs.org/api/options-data.html

In the Guide, the Options API has its own section while the Composition API is nested within the "Advanced Guides" section.

https://v3.vuejs.org/guide/introduction.html

If you check the React docs most examples still do not use hooks and we know how that turned out.

https://reactjs.org/docs/state-and-lifecycle.html

Agreed. That's generally how these things are introduced. It's a shame, because Vue as it currently stands, offers impressively simple answers, to many complicated UI development questions.