Video

oh my god friend you will never believe how useful this video was for me and how many concepts you helped me to grasp ! Thank you very much , i love you i wish you the best <3

First of all, great video! I was struggling to find some good comparison as you did, nice job! At 9:26, actually the whole React JSX gets rerendered. That's how React works: whenever a state (useState) changes, the whole function will be executed, including the render/JSX. There are no exceptions on this. There are no actual "dependencies" for the JSX render, it's just about the state changes. It's behind the scenes that React decides whether a node should be "committed" to the DOM, i.e. change the actual DOM nodes: this phase is called "Commit", and it's the last one of the whole rendering process. But this is something we shouldn't care much about as devs, we just have to know that the whole function/component gets re-executed and re-rendered. When you "opt-out" a variable from the reactivity as you said, it just ensures it remains the same (not reassigned, meaning the function inside useMemo is not called) unless an element in the dep array changes (strict equal ===). This is just about expensive computations of that specific variable, therefore it's quite rare to use. Anyway, I loved how deep you dived into these things, which could open up a lot of thoughts into various aspects of both tools. Thanks for the video!

Thanks. Quality explanation.

Excellent

typescript already gives you warnings if you try to edit a const array or object litteral

Hello, I was analyzing your CZcams channel. your you tube SEO score is zero. It should be increased. and subscribers ,views , like, comments is very low according to your channel age. This is why your you tube growth is very low and your channel setup is also having many problems. If, you can solve this problems your channel will grow and be famous very quickly.

Thank you for creating this video. It was extremely helpful.

Now this is something I'd highly recommend any JS developer to watch

Great content. Thanks

Just amazing, every new person getting into web dev should watch this video. I can't believe you don't have more subscribers.

Nice explanation! I loved how you compared Vue.js and React. Please post a new video explaining how code is compiled in both frameworks step by step

One question: if webpack bundles everything (including third party modules) into bundle.js, doesn't that ever get too big for the browser? The Gatsby library has 1200+ modules; I would assume the bundle.js would be absolutely massive.

Came here after the beef between Evan You and the guy from TsCoding Haha. Really interesting stuff really. Great video! Thanks, man.

This is a phenomenal video, thank you!

awesome video man ! i do have a quick question tho , when you reached the part of using react and imported React from 'react' what tool was responsible to resolve the location of 'react' or to be more precise the actual location of the file that contains the React object

Actual web development

At least four new allocations on every count update in this React component. And zero in Vue

It's a bit unclear and i haven't see some good explanation how does vue know that there was a change in some of the ref variables. Like is it some setInterval that check it or some hidden setter function?

What a gem! Love that you included the error solving parts and the "single take" nature of the video. Liked, subscribed, and added to a playlist)

Great video. This is exactly the type of breakdown I was looking for.

Thanks a lot fo the tutorial !

For the Vue side, it appears to me that you have a function called watchEffect, but when the button is clicked it is calling a function named onClick. I don't understand this.

you got a subscriber here

excellent resources alway hard to show up on searches on CZcams. You are Amazing mate

This was awesome! Thank you for making this!

This is amazing. You're a genius. You made it so easy to understand.

Great vid as always 🌹 Wonder if the vue code is valid 🤔 click=onClick …. Fn click=onClick2() …. Value,Void,undefined If it’s invalid, sad that vue doesn’t give an error despite being ts. Might be a big reason why enterprise would choose react 🤷🏻‍♂️

This is gold

I'm glad this video exists

Nice video ❤ However you don’t need a deferred promise for this. I’ll be happy to edit the code for you if you post a gist 🌹🫰🏻

0:47 not very important but potentially good habit/convention for both readability (separation of concerns) and consistency with vue's approach: you can extract the anonymous function from the jsx into an appropriately named const and then just simply pass it in the jsx event. this way any changes you make to the logic will be done in the logic part of the code (just like in vue) and if you are writing a more complex function it would look ugly and clutter the jsx. this way, simple or complex, your logic consistently shows up where its expected and you and your team will frown less :] edit: the reason i mention consistency with vue is that its easier to switch or be good at both the more similar they are, in general

Great video but I think your explanation at 9:40 may cause someone to think React does not return "new" JSX

Hello Miller. Really am v happy from your channel. can you please make one medium TDD application? OR If you have means, can you share it with me ?

Really very nice.. Thank you so much miller 🥰

Really great video

Beautiful

thanks' a lot man <3

How are you managing to run Vue and React at the same time? Are you utilizing micro-frontend technology on this example?

Finally someone that explains the problem that is being solved by these stupid installs lol. 10/10 vid.

This is great, thanks!

a lot of react slander on the CS. i am still a react fan. but this video is a good comparison between both.

"We're not sane, we're INSANE, we're modern web developers" LMAOOO

❤

Nice overview, as always! I'm doing a refactor of a legacy Rails app form to Vue and we have a mix of "Server config driven" + "Reward Early". We didn't want to discard the existing base field "rules schema" coming from the backend but, at the same time, we want to improve UX as the form is very complex/big/stepped. From my experience, the major problem with the "Server config driven" was dynamic/conditional field validation: a "field B" is required only if "field A" has a certain value. This led to duplication on the front end as we didn't find any good solution to share those rules and is indeed a source of bugs/inconsistencies. In some cases where the validation logic was so complex, we drop the client-side validation of that field and render the error only after validating on the server, so it is more of a hybrid approach! Thanks for another insightful video! Keep it up!

why god , why

You've got my subscribe. More videos like this please!

Great

Another useless feature. Vue project built 2 years ago is totally obsolete and doesnt work anymore. Talk about reliability, total failure. Next please

Good explanation! Thanks

Great stuff. I am starting to hook on Vite. One important thing I hope Vite had out of box is Module Federation, which is quite essential to build micro-frontend. Do you have any idea how to build micro-frontend with Vite?