The next videos will dive deep into scalable architecture in Vue apps, showing you how to structure your projects for long-term success. 🚀 Make sure to subscribe and hit the notification bell so you don’t miss out on those advanced Vue topics! Drop a comment if you have any questions or feedback. I’m here to help!
Great video, however I found the example on receiving props on vue quite outdated, especially in the case where you'd be using typescript. Now in 3.5 we can easily destructure props so the syntax is much better too
Thanks for the feedback! 🙂 Vue 3.5 was just about a month old when the video came out. I might make a video just on this update, thanks to your comment.
Great video! I'll add my two cents. The example with doubleCount is not entirely equivalent in other situations. Computed values are cached and recalculated only when the reactive objects used inside them change. In React, the value of doubleCount will be recalculated on every component render (changes in any local state or render from the parent component, including context changes). The analogue in React is more like useMemo.
@@c01nd01r Thanks for the great point! You're right, useMemo is a good analogy for React. But another edge Vue has is that computed properties use lazy evaluation, only recalculating when dependencies change, which can be even more efficient than useMemo. Appreciate the addition!
The next videos will dive deep into scalable architecture in Vue apps, showing you how to structure your projects for long-term success. 🚀
Make sure to subscribe and hit the notification bell so you don’t miss out on those advanced Vue topics!
Drop a comment if you have any questions or feedback. I’m here to help!
Even as a Vue developer this is quite usefull!
Awesome video, keep it up 🙌
Thank you!
Is it just me, or Vue is way much easier and cleaner than React?
Great content. Thank you!
My pleasure!
Great video, however I found the example on receiving props on vue quite outdated, especially in the case where you'd be using typescript. Now in 3.5 we can easily destructure props so the syntax is much better too
Thanks for the feedback! 🙂 Vue 3.5 was just about a month old when the video came out. I might make a video just on this update, thanks to your comment.
Thank you, thank you very much
Welcome! Subscribe for more, next videos will be all about scalable architecture with Vue 😊
👍🏻thank u!
Great explantation
Glad it was helpful!
nicely done
Thanks!
Great video!
I'll add my two cents.
The example with doubleCount is not entirely equivalent in other situations. Computed values are cached and recalculated only when the reactive objects used inside them change. In React, the value of doubleCount will be recalculated on every component render (changes in any local state or render from the parent component, including context changes). The analogue in React is more like useMemo.
@@c01nd01r Thanks for the great point! You're right, useMemo is a good analogy for React. But another edge Vue has is that computed properties use lazy evaluation, only recalculating when dependencies change, which can be even more efficient than useMemo. Appreciate the addition!
❤❤❤❤😊
pick an original logo, this one looks a lot like fireship's
Done