Why the Vue 3 Composition API?

This Vue 3 Composition API tutorial makes it clear why the limitations of Vue 2 led to the creation of Vue 3's Composition API, and how it solves a few problems for us.

We'll go into detail about some of the challenges you might face with Vue 2, so that you can see where the new API comes in.

0:00 Introduction
0:12 Limitations when using Vue 2
0:42 1: Large components can become hard to read & maintain
3:27 2: No perfect way to reuse logic between components
6:14 Vue 3 Composition Functions

[danielkurz]

This is what I love about Vue so much: it's fresh, simple, and grows by looking back on itself and the industry around it! good stuff

[NicholasMaietta]

I am so glad I started looking at VueJS to solve my front-end development challenges. Seeing this video about the Vue 3 Composition API makes it clear to me this is the right direction for me as a beginner in Vue. I've been fighting rebinding problems after ajax calls in my jQuery and native JS applications and have been thinking more and more about (and planning) for production ready code rather than my garbage ways for so long. I appreciate how you put these videos together and look forward to seeing more from you. Thank you so much.

[PureAlbania]

I've been using Composition API for some weeks now and it's truly adicitve.
The code gets so clean and reusable.
At first it all seem confusing and not understanding the advantages but quickly start loving it and now won't be going back.

[taylorsmurphy]

The only thing is people always forget to change the favicon, so research presentation pages have the vue icon at the top 🤤

[TheDaple]

Excellent, short and concise! Like the part you are showing the disadvantages of older syntax.

[ProgrammingwithPeter]

This is just right on point and clean. GREAT! Not even Evan could explain it like that, he still got beginners confused, you did a better job.

[tommyagnew]

Excellent explanation Gregg, and good job selling the reasons why Vue 3.0 is an improvement in several areas. Hopefully your series will reduce the fear of updating legacy Vue 2x apps that some of us have.

[Selbstzensur]

Oh this is great for sharing functionality between components. I was looking for something like this. As a workaround i was creating new prototype functions the vue object in main.js.

[aaron]

I swear to my neighbor's cat, the way Vue Mastery instructors explain things, it's very easy to understand, with their simple examples, breaking topics to a smaller topics, how I wish all instructors are like them the world would be a better place

[KresnaPermana]

Amazing explanation! How did you make that smooth and sleek animation on the video? Would you like to share what software to made a video like that?

[oriolcantarellisala]

Fantastic!! I love Angular and React but I also love Vue!! Is so simple and adaptable!!

[Pyraptor]

"They are called useSearch and useSorting"... Where have I seen this naming convention before... 🤔

[scottamolinari]

Great video. It's just missing the last part promised at the start. The TS support. How does the Composition API support TS better?

[nnjaFcpalm]

I really need to try learning this when I get time. I know how to use Vue 2, but this composition API looks awesome.

And yeah, the fact that it's more vanilla than Vue 2 and more flexible is nice.

[Techniplexus]

How are using composition functions that different to using mixins or mixin factories? They seem to have similar downfalls and your presentation ends before you have addressed this?

[MrAverageViewer]

You tutorials are fantastic!! The visual animations, coupled with clear explanations, and simple examples, are what really standout!!

[MrChickenpoulet]

does anyone have an example of the mixin factory ? Thanks

[kaanersoy]

Thanks for that perfect explanation, that's the why is Vue.js is the best 👏

[michalgallovic]

I look forward to this feature, reusing logic using mixins worked okayish, using slots was hard to read for others that did not write the initial code or even for yourself after few weeks 😄

[Hiandbye]

Can I think of this like php traits? Because that's what the names useSearching and useSorting remind me of.