4 ms·
> competition api We know you meant "composition api" but while I agree there are some good improvements sprinkled in Vue 3, I deeply lament now that we have l
by montroser 5y ago
> competition api
We know you meant "composition api" but while I agree there are some good improvements sprinkled in Vue 3, I deeply lament now that we have literally two core competing APIs -- the classic "options" api, and the newer "composition" api.
Now when starting a new project there has to be a debate. Some people will advocate for trying the new thing, and as many others will be more conservative.
Worse, within a project there is now opportunity for competing technical approaches allover everywhere.
- samwillis 5y ago> We know you meant "composition api" Yep, dam auto correct. Thanks!
- shrew 5y agoTo be fair, React has been pulling this type of thing version after version. It seems like we MIGHT be settling on functions and hooks now, but only time will tell. The real kicker would be if they removed the options API, for small components, it's all you need and I find prototyping with it easier than the composition API. So I for one am hoping they don't drop support for it in Vue 4!
- synergy20 5y agoReact does the same in fact, and its documentation for class-based and hooks-based are not up to date last time I checked. I would rather having two clearly separated but documented options in vue3(class-based vs functional-based), instead of React's "we're mostly likely just use hooks alone in the future but oops our documentation is pretty much still non-hooks yet".
- zeorin 5y agoThey're fixing that: https://beta.reactjs.org/ https://beta.reactjs.org/
- deleted 5y ago[deleted]
- pier25 5y agoPlus the basic SFC syntax which seems inspired by Svelte: https://v3.vuejs.org/api/sfc-script-setup.html#basic-syntax https://v3.vuejs.org/api/sfc-script-setup.html#basic-syntax