Love/hate this talk. Cory makes great points and I agree with most of what he says. What I don't like is the utter lack of examples

This was so informative. Thank you Tejas

2024

Gem of a presentation! Everything my team and I have learnt sometimes painfully in Production is all here. Even if React 19 tries to address many of the pain points here, this presentation will be relevant for a long time in my opinion. Thank you!

Great attempt to distill a lot of knowledge in a compact presentation! Presents a map of key areas which should enable curious engineers to dive in for their own exploration when required. 👋👋

Freakin awesome.

It's kind of hilarious that if you go to a Vue conference and ask if developing user interfaces is easy, you'll see almost every hand go up, but you go to a React conference and ask that literally not a single hand goes up.....

Awesome talk. Wonder y its only got a few views.

Can someone explain what he mean by fork your render @24:38

Elm is such a delightful language to build applications in.

Beautiful talk! Loved it!

What is this book Ken mentions in the beginning?

What a powerful talk. It's going to stay with me a long time for sure

Starts at 14:30

Wonderful talk Shirley! You can always have your space 👌🏻👌🏻👏🏻👏🏻

You are amazing🎉

Great talk. I've been following David and using XState pretty much since his 2017 talk

5:45:18, Mark Erickson on React rendering behavior

I'm a React dev since 2018 and created a bunch of hobby frontend libs myself and I also looked at all the other options and how they do the rendering, my conclusion is it is not about VDOM or no VDOM or Signals or no Signals, it all comes down to what is running on update, and this is where React made a mistake, React is re-running the whole component with all it's logic instead of just the template/jsx. The next step for react should be a renderer that keeps component state and just re-runs the template, this would make hooks like useCallback obsolete.

such a great talk!

Very very good, thank you Cory

This is one of the best talks I've seen in a long time

no way they nuked context selectors 😢

AWESOME!!

Great presentation 🎉

Great talk! Now all of those tweets make sense! With Cory's voice, those are more welcoming. I hope he will start doing fireship style100 second video on topics along with his tweets.

💯🫡

the x axis is Angular 💀💀💀💀💀💀

wao so good😮

That was a great talk and really put the things the industry is going through in perspective. Thanks Kent C. Dodds.

His talks are the best! ❤ kzfaq.info/get/bejne/jLthga6Jm7fPqJc.html

funniest react talk 2023 😂

Yooo new video ❤

thick accent

interesting thing to take into consideration is that despite the name, react has nothing to do with Functional Reactive Programming. And the industry in general has confused what is FRP and has nothing to do with any of the other libraries like Rx.Js etc.

the lost mathematician wasn’t excepting react + algebraic effects :/

For a very very very simple games yes. That would suffice. But FPS (frame per second) is a thing and not every computer is powerful (or even mobile for that matter). React it is not designed for games and re-rendering things takes a HUGE toll on the whole thing the browser will be repainting over and over and with addition of sprites and everything the game would def be a nightmare. Canvas is a must.

So he bullshitted his interviewers into hiring him and now he is bullshitting a bigger audience, this guy never stopped pretending. Though if you're really just working on small, short-term projects for clients that you will never hear from again, this advice has some value.

tough crowd

Is there GitHub repo?

The future: Algebraic Effects

"So, we are not actually going to look at the implementation of ChildReconciler, because... I love you guys, it's not fair." I can't stop laughing (It's actually true, tho)

what a chad!

Very well explained, thank you!! ❤🙏🌹

Kent is a comedian and best teacher in the world <3

How is this even connected to React??

Thanks @Preethi K, 4 yrs later it's still relevant and it will remain so. I just wanna get out of this aspiring developer mindset and tell myself that Im ready to hit the market. Then fail my way to success.

The Push/Pull 2x2 chart at 21:23 seems really important, but is there any source for this? I want to learn more about it. Also I think I once saw a version of this chart with *coroutine*.

Note for newcomers: DOM’s addEventListener is akin to an Observable’s subscribe method. When reading btn.addEventListener("click", handler), btn is the Observable (instance), addEventListener is that observable’s subscription method, and handler is the callback. ie. source.subscribe("click", cb) where "click" is merely a way to tag-filter events from the source. tl;dr: addEventListener is no more a coupling API than Observable is a decoupling pattern. Coupling is and has always been there, for an event consumer must bind to an event provider, either directly (strong coupling) or indirectly (light coupling).

so many questionable statements.