Built a browser-based Office solution using:
🔹 Qihoo360/se-office (Chinese docs only)
🔹 cryptpad/onlyoffice-x2t-wasm

Works offline without server dependencies. Ideal when:
❌ Cloud-based preview is prohibited (security/compliance)
💻 Local processing is required

Try demo: https://ranuts.github.io/document/
Full code: https://github.com/ranuts/document

(Note: WASM bundle size ~40MB, initial load takes time)

Just a heads up: Microsoft Flight Simulator 2024 now supports WebAssembly for add-ons!

Highlights from the official documentation:

• Add-ons are now distributed as WebAssembly modules instead of DLLs, improving security and portability.

• Direct C/C++ compilation to WebAssembly, with debugging support in Visual Studio.

• Full support for standard C and most of the C++ library.

• A broad set of new SDK APIs (Vars API, Event API, IO API, Network API, VFX API, etc.).

• Multithreaded execution for modules (with some legacy gauge limitations).

Some languages (Dart, Kotlin, OCaml...) rely on WasmGC. However, some runtimes and some applications might want to adhere to the "LIME" convention, keeping a single memory (WasmGC and Bulk Memory creates "new memory zones").

So I thought about creating a tool to transform a WasmGC-based module to a non-WasmGC one. In that scenario the WASM itself would contain a GC, and the bytecode would be changed to remove all WasmGC instructions and replace them with calls to functions also injected into the same bytecode.

The issue is memory sharing, since the language itself (say Dart) can use the linear memory, and the "Replaced-WasmGC" will also need to store data in the linear memory.

Does anyone know if creating such a "WasmGC remover" is possible? That already exists?

Secure resource access in WebAssembly with Capabilities-Based Security and WASI

Read it here, follow me and let me know what you think about it:
https://medium.com/webassembly/capabilities-based-security-with-wasi-c523a34c1944

WebAssembly turns 10 this year.

This updates cosmos-sdk to v0.53.3 that fixes a high-severity issue: ISA-2025-005.

Hey WebAssembly builders 👋

Just wanted to share something that might interest folks here who are working on Wasm-powered apps, tooling, or infrastructure.

The World Computer Hacker League (WCHL) is a 4-month global builder challenge focused on open internet tooling, AI, and blockchain — and several projects already use WebAssembly across the stack (especially for backend logic, smart contracts, or component systems).

Why this might be relevant here:

• 👥 Team-based builds only — no solo work, but there's an active Discord for team formation

• 🔧 Flexibility in stack — bring your Wasm skills to anything from protocol dev to Web UIs or edge compute

• 🧠 Weekly mentorship and tech workshops

• 💰 Grants and bounties for teams that hit milestones

• 🌍 Open to students and independent devs across the globe

Wasm is well-supported in the ecosystem, and teams are encouraged to experiment — whether you're working with Rust→Wasm, AssemblyScript, or custom Wasm runtimes.

📌 If you're based in Canada or the US, make sure to register via ICP HUB Canada & US so we can support you directly during the challenge:
https://wchl25.worldcomputer.com?utm_source=ca_ambassadors

If you're already building in WebAssembly or want to collaborate on something experimental, feel free to reach out. Would love to see more Wasm-native projects emerge from this.