Guy Bedford retweeted
Your AI coding agent isn't slowed down by inference time alone, but by harness assumptions that treat process exit as the prerequisite for tool output consumption
In samsaccone.com/posts/harness… I explore Time to Awareness (TTA) and a path forward to unblock harnesses running human-centric CLIs to accelerate the agent iteration loop.
Guy Bedford retweeted
so @duckdb 2.0 compiled to wasm works well in @Cloudflare workers with emscripten support that launched today, some cool stuff possible.
Guy Bedford retweeted
This is black magic AFAICT

ALT In testing we’ve been able to see significantly improved library compatibility for Rust Workers. To illustrate the sort of capabilities supported, we were able to get a Rust-native Minecraft server (Pumpkin) running inside of a Durable Object with TCP ingress, using real TCP sockets via Tokio. See the end of this post for a full description of this port.
we've been upstreaming changes to make wasm-bindgen able to target wasm32-unknown-emscripten
and contributing back to Tokio, so that it just works on Workers and in Node.js
WASI = YAGNI
proper support for JavaScript runtimes was the real missing piece of the puzzle...
blog.cloudflare.com/rust-wor…
How we got a Minecraft server running with WebAssembly on a single-threaded Durable Object with Cloudflare Workers.
This involved a lot of work to fully support Tokio on Cloudflare Workers with the Emscripten target to allow full support for Rust native applications.
blog.cloudflare.com/rust-wor…
Guy Bedford retweeted
Lots of great birthday week announcements, but this is probably my favorite. I have a huge soft spot for Rust and for WebAssembly and it’s been fantastic to see my peers push Rust in Workers further than I ever did.
Also, using the internal demos meeting to play Minecraft hosted on Workers is probably one of my favorite demos.
blog.cloudflare.com/rust-wor…
Guy Bedford retweeted
Panics in Rust Workers were historically fatal, poisoning the entire instance. By collaborating upstream on the wasm‑bindgen project, Rust Workers now support resilient critical error recovery, including panic unwinding using WebAssembly Exception Handling. cfl.re/4cFnjJR
We recently undertook an effort to improve reliability of Rust Workers, which involved implementing panic=unwind and abort recovery in wasm-bindgen using WebAssembly Exception Handling. Excited to be able to share this work!
blog.cloudflare.com/making-r…
Guy Bedford retweeted
you asked, we delivered :-) blog.cloudflare.com/nodejs-w…
Guy Bedford retweeted
What if Python had static type safety & near-native performance?😉
That’s what python.mbt brings in the latest MoonBit Pearls article.
A deep dive on Python + MoonBit integration
👉 moonbitlang.com/pearls/moonb…
Guy Bedford retweeted
Say hello to my very old friend @UseExpressJS running on @CloudflareDev workers!
Guy Bedford retweeted
Node.js 24.5.0 is out, featuring:
- Built-in proxy support for `node:http(s)`
- Experimental WASM modules
- Upgraded OpenSSL version
💚💚💚
All the details here: nodejs.org/en/blog/release/v…
Guy Bedford retweeted
I'm working to improve the compression rate of the @swc_rs minifier!
Current status:
Total (gzipped)
swc: 12.61MB
terser: 12.66MB
Size ratio: 99.56%
swc produced smaller or equal output for 2128 files out of 2212 files, 96.20%
Details at github.com/swc-project/swc/i…
Guy Bedford retweeted
🚀MoonBit Beta is here!
After 2 years of fast iteration, MoonBit enters its stable phase with regard to language syntax!
✨Built-in async
🛠 Fast tooling and IDE-aware error handling
moonbitlang.com/blog/beta-re…
Microsoft got npm for a steal, and they're barely even running it properly. The npm changes feed API has been completely broken for ~2 months. It's impossible to build apps that sync to the npm registry right now. Really shitty stewardship.
Revision numbers don't match, sequence numbers are out of order, and right now I'm finding it impossible to sync to the feed without ending up in a "sequence number cycle". They broke the meaning of revisions and sequence numbers from the couch interpretation.
Not to mention the API being non backwards compatible. See how many issues folks are brining up in github.com/orgs/community/di… without any recourse. Just simply at the receiving end of broken APIs.














