1. State machines good. I think that's a TLDW for every David's talk (unless it's about animations) :-)

  2. Dan's currently updating the docs. Reminder this is the advanced part , useEffect is very powerful. Again don't look at this document as a need to, but rather to inform you because it's lengthy. Ton's of people wanted these things added to the docs:

  3. Okay what I understand is that React 18 is making me change where I fire async network calls, because I do not want those firing twice. Oh, and its not immediately clear how this common use case is handled. great.

  4. This is classic React, the most common features are either missing cause its a LiBrArY or tedious af to use, then hundreds of 3rd party solutions comes out, the community asks core team for a standard implementation but gets gaslighted for years cause "they are using React in the wrong way", then the feature is finally added, but it is tedious to use and doesn't cover all use cases, rinse and repeat.

  5. What is one clear benefit that you see for using the new useSyncExternalStore? What specifically does this hook give you that the state plus use effect hooks didn't in the pre react 18 era?

  6. Can you point to any other videos that describe the issues with useeffect that you were trying to get across? I'm not sure I "got it" from the talk you gave.

  7. Welp... this just scares me into switching to a different framework. SolidJS/Svelte just started to make more sense. Why is it so difficult to run something on component mount?

  8. Because the React team treats the browser as a compile target and nothing more. The motto for React was "write once, run anywhere" for a while after native came out. In that world, React is the VM scheduling everything and "component mount" doesn't fit in their philosophy where everything is unstable and can happen at any time, however many times.

  9. On an unrelated note, what kind of hell typeface is that in the screenshot where you can’t differentiate parentheses and square brackets at a glance 😑

  10. Not only does this happen, I regularly see code similar to this, and the effect isnt even a side effect ;D one state update triggers another one and that triggers another one in different useEffects...

  11. Why ecosystem of Javascript and its libraries doesn't get stable. Rather than creating something most of the time got spent in learning new tools and methodologies.

  12. Yup, I love Xstate (and state machines in general), but it's very much a tool for a specific type of job. I'm fighting this battle at work right now, where some people want to jump into xstate with both feet without stopping to ask "What problems do we have, what problems does this solve, and what will we use to fill in the gap between them?" That mindset is how we found ourselves mired in the rxjs/redux-observable/epics combo, and have only just recently gotten out of that with the new features of RTK (query and listener middleware). Shoutout to

  13. I'm a little confused because I've been using useEffect to pull data. Where do they want this to happen now? You go to a new page of an app, rather than fetching the data at the component level, you're supposed to fetch it at the router level? Without using other libraries just using React, React Router(optional), useReducer, and useContext, when/where are we fetching the data?

  14. My interpretation is that you wrap the usage of useSyncExternalStore by your own useMyStore and you’ve got yourself a library. Before this, people were using

  15. People use useEffect to pull data o.O? I only use it to react to the data that was retrieved from the backend lol

Leave a Reply

Your email address will not be published. Required fields are marked *

News Reporter