Very excited to announce that we'll have Guillaume Binet talking about Copper Robotics and Robert Balicki (👀 @IsographLabs) talking about Isograph presenting at the next RustNYC! (Note that it's at a new venue!!! DataDog in Times Square!)

Isograph has 2^3 * 3^2 * 5 stars! What a nice, round number! And, one per degree! Please don't add any more stars, it will ruin the beauty of the moment. github.com/isographlabs/i…

This is a great talk! The key things to note about fragments are that a single function should read a given fragment (i.e. they're not for reuse). Isograph is an entire framework built upon taking that to its logical conclusion! Associating these statically is great: - if

Relay and Isograph solve this!

👀👀

Honestly, the best part about this is **how great the DX of implementing it is**. The VSCode extension asks for what it needs: to resolve where the cursor is (on a field of type Pet) and the list of fields on Pet. And that seamlessly integrates with our incremental compilation

Just shipped a nice perf improvement: entities (i.e. types like "User" and "Query") no longer carry location information. So changes to unrelated entities mean that we can reuse functions more aggressively! Compare the before- and after-. In between, I modify the schema.graphql

Incredible to see how polished Isograph’s workflow has become. Autocomplete + incremental compilation = serious productivity gains.

GraphQL And there's more coming!! There's a feature that we're working towards that will blow everything else out of the water (and not just in the GraphQL space.)

🫶

In the next version of Isograph... diagnostics showing up in VSCode!! (Clearly not perfect... the location info is off on the second diagnostic. But still a massive improvement.) And (I'm a broken record here), but thanks to the underlying work we did on pico (our