Kevin Saldaña

I think the biggest hurdle for me was understanding the fragment philosophy in Relay and in particular the type emission story and the flow of types. Once I got my bearings on that tho the power of the paradigm was very clear. That story is even better now with concurrent mode.

Thanks for the detailed examples of the new experimental Relay version @en_JS! I hadn't used Relay before, so it was a lot to grok at once—but your comments and code made it possible for me to figure out all the individual pieces, so thank you!

Having some external orchestrator (eg Redux) seems like a decent solution. UI fires event -> preloading of data and the transition itself is dispatched to some higher abstraction. However looking at concurrent docs it seems that this pattern is a bit at odds with the architecture

It's quite awesome to see all these disparate features comes together with really cool emergent properties—that's good design. Reminds me a bit of how I felt about @typescript when conditional types and inference were introduced, and how suddenly all these features opened up.

A parent event handler having knowledge of an immediate transition is coupling those views together a bit. Obviously for reasons that once again provide a better DX, just interesting to think about when working on large code bases with many teams (which obviously FB has xp with!)

The preloadedQuery APIs in Relay are interesting. I understand why it would be the preferred pattern from a UX perspective. Feels slightly at odds with some of the other Suspense features, which allow for better separation between parent -> child relationships.

Lots of great talks from #ReactConf2019 —still wrapping my head around some of the concurrent patterns. The docs from @dan_abramov are fantastic! Trying to get up to speed with Relay since I don't have much experience with that.