Iβve been drawing up an overview of pure vs GraphQL fragmentized [React] UI components, different ways to propagate data through the tree, and the associated maintenance/performance considerations.
Perhaps you find it helpful or let me know if you have any feedback! π
@sakesun@MicrosoftTeams@RelayFramework@reactjs@GraphQL Gotcha. I wouldn't say Edge and its needs are representative of many other MS products. There's a lot more React in those, and that's not going anywhere anytime soon.
This past year at @MicrosoftTeams, I've had the pleasure to lead the UI architecture for part of this new Chats and Channels UX, and introduce @RelayFramework to our @reactjs stack to use @GraphQL the way originally intended. Coming soon to 320+ MAU π
https://t.co/ALZIljp8vF
@craigajohnson @___zth___@MicrosoftTeams@RelayFramework@reactjs@GraphQL These decisions are not made in a vacuum. Blazor or anything else that amounts to a full rewrite is remotely not a choice given the existing constraints.
@MicrosoftTeams@RelayFramework@reactjs@GraphQL We also started writing some docs to explain how GraphQL and React were meant to be used together through fragment composition, and how we want our engineers to use Relay from day 1: https://t.co/Zbh5w50Qwd
@Eli_White Thanks, man! We're already loving it very much! Sorry to have missed you in Amsterdam, I went heads down awol π Hope to see you on this side soon!
Does anyone know of a great resource for modern React that explains the need for composition > inheritance and how to do it?
I think this one from the legacy React docs still applies, but it's a bit short and too easy to conflate OOP and Prop inheritance https://t.co/eT8MUYPPbu