Differences between Vue and React?

Discover how Vue and React differ in this segment from our full Vue for React Devs course 👉 www.vuemastery.com/courses/
Ready to master Vue.js? With Vue js tutorials on the latest topics, and exclusive content with Evan You (the creator of Vue), Vue Mastery is the ultimate learning resource for Vue developers to elevate their skills. Watch more free Vuejs tutorials 👉 www.vuemastery.com/courses/
0:00 Leverage your React knowledge to learn Vue fast
2:16 Computed Properties
6:55 Other Functions
7:50 Keep watching this course on VueMastery.com

[@VueMastery]

To watch the full Vue for React Developers course, visit: www.vuemastery.com/courses/vue-for-react-devs-similarities/intro-to-vue-for-react-devs

[@morlz]

vue 3 is just great, I like it much more than the second version. The addition of hooks and composable finally made normal code separation possible. Working in a large team is much better with vue 3. Thank you!

[@PierreLaBaguette]

the video isn't really about "the key differences between vue and react". it's just a tutorial/intro to vue..

[@samuelmorkbednarzkepler]

Love vue 3

[@simonpavlik8952]

Can somebody please tell me what theme and font type is he using? It looks awesome!!

[@jahongirbektemirov6516]

Vue 3 is so great 🎉

[@khaledsanny4817]

Clickbait title... seriously you just loosely compared useState to ref and completely forgot about the topic right after ... just why ?? its a bit annoying

[@xamantiwari]

🤣😂🤣

[@melyssal.9397]

bc they want you to buy their course

[@esdegan7176]

RIP react, RIP flow, RIP metaverse, RIP facebook.

[@PierreLaBaguette]

why??

[@TheDeprecatedLibrarian]

Theme?

[@bradstoney2325]

React has the useRef hook though. It works the same way Vue's ref does.

[@notkamui9749]

no, not at all. It will never trigger rerenders

[@daycoder301]

i love vue

[@niravpanchal4291]

I love vue too

[@emberchord]

omg, I'm screaming - did you add sound effects for the typing too, lol that's hilarious

[@jaredbecksfort1976]

How is this a video about the differences between Vue and React? There was about 20 seconds of that and the rest was just a Vue tutorial.

[@jeanrodrigues6249]

sudo call

[@christianm4906]

React js is just annoying. I regret the time spent learning such as messy library just because it is popular.

[@R3AktoRMacedonia]

Vue 2 was good as it was, all this "new features" like hooks (which are basicly callbacks) are concepts invented in the 70's. Please stop following fashion trends from other frameworks just because some "developers" get "excited" about meaningless things.

[@combattanta7577]

I think you're being reductive when you say that. Just because you don't experience the pain points that other Vue devs have from Vue 2 that Vue 3 solves, doesn't mean those pain points in Vue 2 does not exist. Vue 3 exists not because of some "trend", it exists to solve a legit problem that Vue 2 unfortunately has especially for large scale apps and libraries.

[@samuelmorkbednarzkepler]

What are you even talking about? Firstly, how can you simultaneously call something a "trend" and also complain that it's a decades old convention? If its such an old concept would that not be the opposite of a new trend? And no, hooks are not "simply" callbacks. Hooks allow you to hook into the Vue reactivity system in a much more modular way than what was possible before. This was not possible in Vue 2 and is a big improvement in Vue 3 reguardless of wheter or not some other framwork had the same idea 900 years ago. Its the entire reason why libraries like VueUse can exist - which is incredibly powerfull. The Vue options API would never in a million years have allowed for that amount of power and modularity from library authors. The new composition API is a great benefit to the future ecosystem of Vue, same as it was for react when they adapted hooks. If its a trend its because everyone loves how good it is. Which it is. But brushing this off as a bad change by calling it a "trend that was invented in the 70s" would be like if xbox released the ability to modularly change their system and then you went: "duuude. Being modular is just a trend. Lego already inveted this decades ago, and the egyptian pyramids before them." Sure dude... In any case, even if you personally prefer the options API (yikes) nothing about any of this is "meaningless." Vue 3 is a massive improvement. The composition API is just objectivley much better at grouping logic togheter and if you dont think so then I dont think youve ever actually had to program large scale systems. If you cant relate to the struggle of writing a large component with the vue 2 options API and being forced to split all your logic up into a tangled web of unrelated boxes then I dont think you have actually ever build a large, complicated vue component before. You can have your own opinion about this if you want but you need to cut the shit if you think this is "just a meaningless trend." At best youre just being unresonable with your own personal opinion and at worst you just dont have any idea what youre talking about.