Video

nice!

I need to stop watching all of these server driven demos from evan bacon. It’s just too much of a tease

Ken's talk has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

This talks is excellent and Ryan is a brilliant speaker, that's why it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!

Ich grüße euch... Hier sind wir schon mal.. Kann ja nur noch besser werden oder?? 😁☺️

legend

0:30 starts

코드는 어디에 있나요?

I think if we just went over to compiling and having the compiler optimize before the code even executed it would go a long way towards fixing Everything that is ultimately wrong with javascript.

Ljubav moa faca jedna 😊

What is the difference wiht monorepo except it generates stuff for you?

Does anyone know if React Forget is going to optimize only React code running in strict mode?

Any activity during winter, shouldn‘t be allowed 😂 Berlin is a summer-first city 😊

Pls aunty Jemima, I've written to you twice about website portfolio development for me. But you've not noticed, why? I'm new in copywriting and would like to use it to get experience and exposure.

The tanstack guyyy🎉🎉

looking forward to use it in projects

really a good pattern 👍🏻

react forget compiler is jusr awesome...we will never have to write manually memoize ever again!!

This is beatiful! Thanks a lot! Also, your presentation about Jest archicture is amazing.

Can’t wait to look at the compiler code

Awesome Confidence

Cool

1:30 Can the compiler automatically prevent developers from writing code this bad? So much for "declarative rendering framework" 2:20 React cares more about performance can code quality. 180° from its beginnings.

Okay, I got the idea of this video: the main idea of this video is to give us more reasons to choose another lib/framework.

thanks

Curious, i thought useEffect would also solve the problem. Anything that i missed? I'm new with react

Good explanation! Thank you so much

Thank you.

I remember seeing Xuan Huang video 2 years ago about this, I didn't think it will work.

hi meghna.same like you my situation.swifted to foreign country year back. i would like to change my career to IT profession.kindly advice me wherre can i start from and how can i get experience in that

wonderful lesson , ThanQ

coming from the blog

AMAZING, will you do an updated tutorial regarding the topic, with the newest next 14?

Such a nice talk

Next time I'd like to hear more about why you guys make the things you do the way you do it.

React js interview czcams.com/video/6DVVJrHrE0U/video.htmlsi=ds2SKiW6785Hlzul

Relatable

thumbs up btn has a bug if you click it fast 😂

Fetching hydration code on hover sounds feasible but if user has touch enabled device (Mobile, tablet, smart devices) then fetching code on click might degrade the UX in my opinion. Can anyone explain? Edit: I think on visible type flags can be helpful in terms of touch devices. Need to dig deeper into docs now.

Excellent talk. I'm a Fintech Developer (NodeJS, SQL, AWS service). Learning the tech was one thing to get my foot in the door, but once on the job I suddenly realised the amount of banking standards. You definitely need to know the legal/standards side of things, as well as the tech side.

7:15 whoaaaaa lol That's exciting, and I'm behind the scenes!

Just imagine how much queries will be going to server per each hydration operation

Great!

For forms, what is the best solution , using useState or useRef ?

meh... whats wrong with standard JS, HTML, CSS, its more simpler, standard and straightforward... anyone who need framework to do web are coders who lack of skill to do the actual coding... framework are the way to do simple thing so complicated...

Amazing! ❤ thank you

It can make developers' lives easier, but I don't think that will be a part of React. Maybe it can be used as a separate utility for quickly boosting the performance of some projects. This approach can sometimes help optimize the code base written by inexperienced developers, but it does not cover all cases, so also can give the opposite result. There are many cases where there is no need for memorization; for example, the "videos" props can get from the API only on the mount and don't change anymore during the live cycle of an application, so there will be no rerenders. I think it's tough to check programmatically if a particular component really needs memorization. For example, let's think about the example in the video. We can prevent <VideoTab> render after changing the heading by removing this from props and then using Context or some "State manager" to get it inside the <Heading> component. In most cases, good component splitting and using a state manager perform better than memorization. Context is a nice feature added by React, but they have many weaknesses compared with "state manage" libraries. In my opinion, the React team needs to add its built-in state manager to provide more flexibility when working with component states.