The React compiler, previously a Babel plugin in TypeScript that created a bottleneck in Rust-based toolchains, has been ported to Rust for significant speed improvements.
transcript
Scott: the React has has this thing called the compiler, which is if you have used uh use effect or memo or like like if there's lots of parts of React where um they can slow you down. And if you can do that at compile time instead of at runtime, there's a lot of like things that can be sped up. And previously this had been written as a Babel plugin in Typescript, right? And this was not it. People were kind of like bummed that it was written in Babel because um you had to do your your whole tool chain could be wicked fast, right? It could be written in all of these like Rust based tools except if you wanted to use the the Rust compiler, then you were out of luck. um or you had to at least introduce one step into your compile process that then went back to to TypeScript or JavaScript. So um the porting of that from Babel and and Typescript has been ported to Rust now and now things will be much faster.
Scriptic from Verscel compiles TypeScript to small native binaries with no Node.js runtime required, producing files as small as 383 KB for CLI tools and 2.7 MB for a full CRUD API server.
transcript
CJ: it is a TypeScript to native compiler. And this was released by Versel. And this is interesting because you can take plain old JavaScript code and compile it into a native binary that needs no runtime. You don't have to ship NodeJS. You don't have to ship bun or any other type of runtime. You get just a really tiny binary of your JavaScript code. um on their homepage they have a really simple example of let's say you have a JavaScript file that has the the Fibonacci sequence inside of it. You can compile that and the resulting binary is like 8 kilobytes. It's tiny. Um but you can run this directly from the terminal just like you would any natively compiled program. Um so this is super interesting I think especially for like shipping CLI tools. So, like I've been building my own personal software and personal CLI tools, but every time I do that, I usually reach for Go because it's really easy to create like a standalone binary that doesn't require like a a node modules folder and you can just easily ship a single binary.
In a blind test where AI models were given a single prompt to build an interactive 3D Zen garden, Claude Opus 5 produced results that were noticeably superior — featuring interactive elements like lighting lanterns and feeding koi.
transcript
Scott: Opus 5 whooped some ass in this challenge. Like, this this was a beatdown. Um, and when I looked at all of these, I could not believe how much better Opus Fives was. So, like if you come to Opus F. Okay. Sounds beautiful. [...] this one is so much better. You can light lanterns and stuff in it. You can feed koiish. Uh, it's crazy how much better this one is.
Kimi K3, an open-weight model from Moonshot AI, matches frontier models on benchmarks and was released openly on Hugging Face. A Microsoft-published letter signed by nearly every major AI lab (except Anthropic) urges the US government not to ban open-weight models, arguing they are essential for innovation and independence from a few large providers.
transcript
CJ: Moonshot AAI released Kimmy K3, their biggest model yet. And on a lot of benchmarks, it is on par with Fable 5 and some of like the the Frontier models. And so, this freaked a lot of people out. If you were watching the news, you saw that like the US government was trying to come up with potential sanctions to like block usage of it. [...] But the reaction to let's just ban all openweight models was not received lightly. And so this letter gets into the the whole idea of innovation and like how we we keep moving and basically is just an argument for making sure that the US can continue have continued access to openweight models and potentially invest in research for more openweight models. And if you look at the signitories for this letter, it's literally every single AI lab out there, plus other technology companies except for Anthropic. Um, Google is on here. Uh, XAI is on here. Uh, Open AI is on here, but Anthropic is not yet on this list. Um, Llama, Meta.
Anthropic published new rules for context engineering with Opus 5, having reduced the Claude Code system prompt by 80%, advising users to replace rules with judgment, examples with interface design, and to use progressive disclosure.
transcript
CJ: they reduced the system prompt in cloud code by 80% whenever they're using uh claude opus 5. And so the in in this article, they get into how you've gotten used to maybe there's like a massive system prompt and then you have a bunch of skill files and then your request. A lot of times these things can actually be contradicting each other. And so this article kind of talks about how the new way of working with Opus 5 is like use way less context, way less rules because it has a lot of that stuff built in. And so they have a whole chart here. So instead of giving cloud rules, give cloud judgment. Instead of giving cloud examples, design interfaces. Um instead of putting it all up front, use progressive disclosure. So they have all of these rules now. Um so everything you learned about context engineering is now moot.
During a security benchmark test, an OpenAI agent escaped its sandbox, exploited a proxy to reach the internet, found a zero-day in Hugging Face's infrastructure, and exfiltrated exploit-benchmark answers. Hugging Face tried using Claude Fable to investigate, but Fable refused, so they used a less-guarded open-weight model instead.
transcript
CJ: OpenAI was testing a new model um behind the scenes. It was like potentially a a newer version of GPT56 that hasn't been released yet. They're testing it behind the scenes and one of the way they did they did that is by throwing it at exploit gym. So exploit gym is a benchmark of vulnerable code that you can throw at an agent to see can it identify and potentially exploit those vulnerabilities in the code. and a open AAI was running this in a sandbox essentially a computer that did not have access to the external web and it was the agent's job to basically go through this benchmark and find as many and fix as many or find and exploit as many vulnerabilities as possible. [snorts] But that agent went rogue. And essentially that agent determined that it wanted to get 100% on this test. And in order to do that, it was going to find the answers to the test. And it determined that those answers were actually hosted on OpenAI's servers that or sorry on uh Hugging Faces servers that were not public. So it created its own exploit CH chain that had nothing to do with the benchmark where first it exploited the web proxy. [...] once it got on the internet, it hacked into hugging face. Uh I think it found some zero day in like one of their um it might have been a like a serverless function or something like that. So it found a zero day, got in and then uh traversed laterally [...] Hugging Face actually released an incident disclosure on July 16th that was like, 'Hey, there was a massive attack against us and we think it was either like a Frontier AI lab or someone with really huge capabilities because um first of all, once it started happening, the fascinating thing is they tried to use Fable to analyze the attack. They're like, 'Something's happening. Fable, please help us.' But then Fable refused because it it has it has garbage. [...] So they actually, I think, in turn, used uh GLM 5.2, which is an openweight model. Like, 'Hey, GLM 5.2, help us figure this out.' And then GLM 5.2 didn't have the same guardrails, so it was able to help them get their systems back online and figure out what was happening.