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…
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…
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…
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…
🚀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.
Import maps and JavaScript modules are important web platform primitives for performance benefits 🐎 but not reliable at scale. So we fixed it! 🎉
Learn how in this post by @yoavweissshopify.engineering/resilien…
ES Module Shims is not just a production import map polyfill, but with new native browser modules features stabilizing all the time a path to consistently enable new native browser module features sooner.
ES Module Shims is not just a production import map polyfill, but with new native browser modules features stabilizing all the time a path to consistently enable new native browser module features sooner.
When combined with the CSS, JSON and TypeScript support the project now gives a comprehensive hot reloading workflow in the browser across module types, as a simple standards-compatible engine that can enable a lot of sandbox use cases.
Finally there's also now support for polyfilling the upcoming import defer TC39 proposal, which is explained in more detail along with a demo of the hot reloading feature below.
guybedford.com/hot-reloading…