A bit of Super JTC Battle in #SuperWodenGP3
Could you please RT and add it to your wishlist? It’s a huge help for us small developers! Thanks!!
https://t.co/9P0UfFVuEK
@vidar_0208 Depends on whether the driver support occlusion query counting result or not. If the driver only support boolean result. We use like 9 proxies. If the driver support counting result I remember 4 or 5 is more than enough.
There are so many great talks in BazelCon 2026. OpenAI shared their rules_rs. "The Sandbox Is a Filesystem" is what our team always want to try. Bazel team are experimenting port parts of Bazel to rust!
The BazelCon 2026 Recap is live!
Inside:
• Highlights: BUILD Foundation updates, Community Survey & photo album
• Recordings: Chronological session playlist
• Notes: All Birds of a Feather & Unconference sessions
👉 https://t.co/jOfw0h6xx4
Introducing InfiniteDiffusion, my independent paper accepted to #SIGGRAPH2026!
I have one RTX 3090 Ti. No funding, advisors, or team. By day I'm a new grad SWE at Walmart.
The paper has two main contributions:
- InfiniteDiffusion: a new approach to infinite generation with diffusion models.
- Terrain Diffusion: the world’s first learned procedural terrain generator.
Here’s why this matters, and how they are connected. 🧵
While rules_rust and rules_rs don't support native rustc incremental compilation within a crate, they enable fine-grained, hermetic build caching at the Bazel action level.
This allows compilation results to be seamlessly reused across different working directories, branches, and even machines through remote caching.
And rules_rs is developed at OpenAI and open-sourced.
Isn't this basically how Google works? Changes are committed directly to trunk as CLs (reviewed and tested before landing), using Blaze (Bazel) to speed up the CI.
Before AI, we didn't need to scale internal workflows like Google, but now with AI, we really need to learn how Google works.
BTW, "Software Engineering at Google" is a wonderful book to read!
A few more thoughts on this:
You still need CI. Instead of a merge queue, your untested stack of commits in trunk becomes a queue that gets tested in batches. Good batches mark safe deployment snapshots. Bad batches will get bisected and reverted automatically.
My now-traditional(?) BazelCon 2026 recap is here! https://t.co/hK8QRqstzV . I'll warn you: it's _long_ and it talks about AI but... fear not, it's not AI-generated. Enjoy!
So basically, Windows needs to become free, or AI agent companies won’t be able to spin up Windows sandboxes and VMs for testing at scale without breaking the bank?
Amp now has macOS Satellites!
Agents can now spawn Macs and build, test and run your iOS and macOS applications on them.
Rolling out now.
https://t.co/vQ6Mpt5gIK
@charliermarsh@ArielKwiat Not sure if it's because our repo is huge or the conversation history is long, but switching threads is really lagging. I had to switch to t3code for this.
Back in 2004, the developers of Ratchet & Clank: Up Your Arsenal patched their game(which had no patch system) by hack their own game with a EULA buffer overflow.