AI Weekly Malaysia

Cloudflare published the first public experimental preview of first-class support for the Emscripten wasm32-unknown-emscripten target in the wasm-bindgen toolchain, letting native Rust and Tokio-based applications run on Workers. The effort was started by Google over a year ago and later reviewed and supported by the Cloudflare engineers who maintain wasm-bindgen. To demonstrate it, the team got the Rust-native Minecraft server Pumpkin running inside a Durable Object with TCP ingress using real TCP sockets via Tokio; experimental patchsets and example repos are available now (Building Emscripten Rust Workers, running the Tokio async runtime in a Worker, TCP sockets with Emscripten and Tokio).

Why: Emscripten support uses Node.js compatibility flags to virtualize timers, filesystem operations, and sockets on Workers, which is the missing piece if you previously ruled out Workers for a Rust crate that needs std::net, file I/O, or a Tokio runtime. It is pre-release, so treat the patchsets as a prototype path for a Tokio service or a TCP-ingress Durable Object, not a production migration; if you have a Rust service you wanted at the edge but kept on containers because of missing native platform features, this is the moment to spike a port. No Malaysia-specific detail appears in the post, so local relevance is limited to teams already weighing Workers versus container hosting.

Nicholas Nethercote's September 2026 roundup measures a 4.57% mean wall-time reduction for the Rust compiler over 2026-07-29 to 2026-09-28, with 555 of 629 benchmarks improving and only 74 regressing. Standout single changes include PGO for Clippy (PR #159642, up to 18% faster on the best benchmark), the LLVM 23 upgrade (PR #158734, mean 1.2%), and Jack Huey's lazy liveness work (PR #161938) cutting serde instruction counts 3-5%. Two large nightly features landed: the Polonius Alpha borrow checker and the new trait solver 'Penelope Hammertime', both more capable but measurably slower in a minority of cases, including the popular serde crate.

Why: If you build on stable Rust, the 4.57% mean gain and the LLVM 23 speedup reach you without code changes, but Polonius Alpha and the new trait solver do not: they are Nightly-only, and both are slower on some crates, with serde specifically called out as a regression case. So the decision is whether to try Nightly now for Polonius's more permissive borrow checking, and to budget for compile-time regressions in your own crates rather than assuming the nightly switch is free. Clippy's PGO win (up to 18%) is also a reason not to skip Clippy in CI on time grounds.

Google has filed an appeal at the EU's Court of Justice against a Digital Markets Act decision that would require it to share user search data with rival search engines by January 2027 and modify Android so rival AI services can interoperate with it by July next year. Google argues its systems are already open and interoperable and warns the directives could cause privacy and security problems; the EU's stated goal is more competition.

Why: This is an EU proceeding, and the text does not say whether any Android interoperability changes would apply outside the EU, so nobody should assume new search or assistant APIs reach Malaysia because of this filing. The concrete thing to track is the two dates in the order — search-data sharing by January 2027 and Android changes by July next year — because if they survive appeal they define the first regulated access route to a mobile platform's default AI assistant surface, which is the shape Malaysian Android app and assistant builders would eventually have to plan around.

Ars Technica's headline reports that a federal judge dismissed antitrust lawsuits from Chegg and Penske that targeted Google's AI search, published 2026-10-01. The retrieved page text contains only Condé Nast consent and cookie-preference boilerplate — no judge name, court, docket, ruling reasoning, or terms of dismissal are present in the source.

Why: There is nothing actionable here: the extract has no ruling text, so no one can tell whether the dismissal was with or without prejudice, what claims were rejected, or whether an appeal is possible. Anyone building on search-referred traffic or licensing content to AI products should wait for the actual order before changing anything.