@[email protected]

GraphQL artisan @Microsoft Teams. Previously React Native plumber @Microsoft Office, director @ArtsyOpenSource, @RubyMotion, @fngtps. Author of @CocoaPods.

[@[email protected] @alloy]

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! 🙏

[@[email protected] @alloy]

@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.

[@[email protected] @alloy]

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

[@[email protected] @alloy]

@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.

[@[email protected] @alloy]

@sakesun @MicrosoftTeams @RelayFramework @reactjs @GraphQL I'm sure some of them are, but there's just so many MS products. I don't know of big name examples in my vicinity. Which are you thinking of?

[@[email protected] @alloy]

@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

[@[email protected] @alloy]

@NeoNacho Old New Netherlands

[@[email protected] @alloy]

My family and I have successfully managed to immigrate to the US and we have just signed a lease to a house in the Seattle Green Lake area. It's been quite a journey figuring everything out (no relocation assistance), but now we're looking forward to a summer of nature trips! 🤩

[@[email protected] @alloy]

@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!

[@[email protected] @alloy]

@NeoNacho Hello neighbour 👋

[@[email protected] @alloy]

@Zephraph Yes! We can go surprise Chris 👻 Are you still in NYC?

[@[email protected] @alloy]

@dblockdotorg @OpenSearchProj Let's do it! Hit me up close to the date

[@[email protected] @alloy]

@katarinabatina Can't be a coinkidink!

[@[email protected] @alloy]

@SmileyKeith Ok, there's only like 7 official ones. I'll find you :P

[@[email protected] @alloy]

@Its_stolt Thanks! We're almost neighbours now :D

[@[email protected] @alloy]

@SmileyKeith Where?!

[@[email protected] @alloy]

@JoshuaPHilll Why is nobody commenting on the voice control system of the car being unfazed? Am I hearing voices?

[@[email protected] @alloy]

@ScriptedAlchemy @BytedanceTalk @rspack_dev @modern_js Congrats!

[@[email protected] @alloy]

@dan_abramov Do you have any plans on having an updated version of the Composition over Inheritance guide on the new doc site?

[@[email protected] @alloy]

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

[@[email protected] @alloy]

@wesbos They also might already be in group 1, they just don’t realize it yet.