Excited for #RustNYC this evening!
Charles Giguere: Powering the Foresight Spatial Labs renderer with #Bevy
@chrisdryden.bsky.social: Cutting Amazon build times by 40% with Rust
Big thanks to our host @materialize.com!
It does exist in one specific way, which is that the compiler generates a bunch of client fields for you: __refetch fields (and some others).
But there isn't any reason you can't write your own "adapter" (idk what to call it) and auto generate components for each form variation.
Would love to hear about what you have in mind!
Right now, Isograph is very pro-repeating yourself (in the Relay way of many fragments with the duplicate selections), which is to say, there's no way to "create many components in a loop" or the like. But we will definitely have that, at some point!
🎤 The GraphQLConf CFP is open!
Got a GraphQL idea or story to share?
Join us May 6 - 7 at Meta HQ in Menlo Park.
Submit your talk 👇
sessionize.com/graphqlconf...
Houdini is one of the most exciting things going in the world of GraphQL right now. Check out the video from the latest conference youtu.be/cRTYf59rYMU
What is an ideal client when GraphQL goes full stack?
So go on, give the quickstart isograph.dev/docs/quickst... a try! Join the discord isograph.dev/discord! Star the repository github.com/isographlabs...!
So what did we achieve? We
- allowed Isograph to be adopted incrementally, and in more situations, while
- substantially improving the DevEx of doing so, and
- shipped support for optimistic updates, which raises the ceiling for the quality of app you can write :)
github.com/corydeppen who added docs about TanStack and StrictMode, and github.com/TheRealGchen who added docs related to troubleshooting!
The team grows!
But what makes me most excited is that this release included commits from **five** new contributors!
The aforementioned github.com/lucasmachadorj and github.com/sp6370, as well as github.com/Cobord, who added tests to the compiler, and...
On top of this, we made internal refactors (quite a lot, actually). These had the effect of letting us ship additional language server features, improving the performance of the compiler and setting us up to support non-GraphQL backends.
Great work by Vadim Evseev here!
Now, the compiler doesn't recreate the entire __isograph folder on every incremental update, but instead just makes the minimal changes to the filesystem that are necessary!
But what we shipped doesn't end there! github.com/lucasmachadorj shipped a change that improved the perf of the compiler. In some local tests, incremental updates went from 144ms to 53ms and 125ms to 72ms. And these gains are likely going to be much larger in larger projects!
This relied on a refactor of the Isograph store. It's no longer a "single object", but rather a stack. Adding an optimistic response is simply adding a layer to this stack, which can be removed without any difficulty!
And this sets us up for some pretty cool future wins 🙈
In cases like that, you can provide an optimisticNetworkResponse that will be written into the store for the duration of the network request, then dropped afterward!
Oftentimes, you know what the network response will look like when you're making a network request. For example, if you are incrementing the star count on the Isograph repository, we can predict the response.
But wait... there's more! We also added support for providing optimistic responses! Check out this video for more youtube.com/watch?v=skWB...
Once again, amazing work by @patrykwalach.bsky.social
And the best part? This API uses all of the same Isograph primitives, you get a bunch of stuff for free:
- re-rendering just the components are affected
- the ability to garbage collect your data when you're done
And so much more!
being able to write arbitrary data into the Isograph store is for you!
You write data into Isograph, and then let Isograph take over rendering part of your page from there.
This makes it dramatically easier (and lower risk) to adopt Isograph in new projects!
Whether you're incrementally adopting Isograph on a per-component basis (and you should demand this of your frameworks!), or you don't have a GraphQL endpoint ready, or you have some external source of data (server-sent events, local storage, external APIs, etc.) then...
But that's enough about DevEx. Let's talk about some runtime features. First, the ability to write external data into Isograph... in a fully statically typed way! Thank you
@patrykwalach.bsky.social for this amazing work.
www.youtube.com/watch?v=Tl5p...
And not only does this work in VSCode, thanks to github.com/sp6370, we're also publishing the extension to the Open VSX registry! So you can use it in other editors! Thanks!!
And most importantly... if you select a field that doesn't exist, the extension will offer to create it for you! Wow!!
Isograph is truly committed to helping you ship fast :)
We now have autocomplete of fields!
Errors are now surfaced in VSCode!
First off, I want to talk about some of the amazing DevEx wins that have landed. Check out this video where we holistically look at the DX of Isograph, before talking about what is new in v0.5.0
www.youtube.com/watch?v=6tNW...
Hey folks! Isograph v0.5.0 has just been released!! The trend of groundbreaking releases continues 🎉
This release includes support for optimistic updates and for writing external data into Isograph. And it has massive DevEx wins 🤩 and huge perf wins.
Let's dive in!
Announcement slide for RustNYC Unconf 2025 featuring a Containers in Rust track. The slide has a mint green background with the Rust crab mascot wearing a Statue of Liberty crown in the top right corner. Text describes exploring Docker-style container internals: kernel primitives (namespaces, cgroups, capabilities, seccomp), and their role in isolation/resource control. See a Rust implementation for memory-safe inspection and tweaking. A circular photo shows Carson Weeks. Sponsor logos appear at the bottom: Materialize, Lawrence Harvey, Empathic, and Antithesis.
Announcing our Containers in Rust track at #RustNYC Unconf 2025!
Join Carson Weeks to explore container internals: kernel primitives (namespaces, cgroups, seccomp) and their role in isolation/resource control. See a #rustlang implementation for memory-safe inspection and tweaking.
rust.nyc/unconf
Announcement slide for RustNYC Unconf 2025 featuring a Closed-Loop LLM Engineering Built With Rust track. The slide has a mint green background with the Rust crab mascot wearing a Statue of Liberty crown in the top right corner. Text describes how advertising companies have used multi-armed bandits to determine what ads to run in what context. The LLM gateway leverages the Tokio runtime, the Clarabel conic program solver, and ClickHouse to asynchronously update sampling probabilities of prompt-model pairs as inferences are being run. Bring your laptop to try it out and maybe win the agent optimization competition. A circular photo shows Viraj Mehta smiling. Sponsor logos appear at the bottom: Materialize, Lawrence Harvey, Empathic, and Antithesis.
Announcing our Closed-Loop LLM Engineering track at #RustNYC Unconf 2025!
Join Viraj Mehta to explore an LLM gateway leveraging #Tokio, Clarabel conic program solver, and #ClickHouse to update prompt-model sampling probabilities in real time. Plus: agent optimization competition!
rust.nyc/unconf
Announcement slide for RustNYC Unconf 2025 featuring a new Safety Critical Rust track. The slide has a mint green background with the Rust crab mascot wearing a Statue of Liberty crown in the top right corner. Text describes the track as focused on all things Safety Critical, led by Xander Cesari, a key member of the Safety-Critical Rust Consortium and Rust Project Content team. A circular photo shows Xander wearing a plaid shirt and cap. Sponsor logos appear at the bottom: Materialize, Lawrence Harvey, Empathic, and Antithesis.
Announcing our Safety Critical Rust track at #RustNYC Unconf 2025!
Join us for sessions on all things safety critical, led by Xander Cesari from the Safety-Critical Rust Consortium & Rust Project Content team.
Register now: rust.nyc/unconf
