News for hackers. Stuff that matters.
Re:WASM 2.0 by anentropic on Friday May 09, 2025 @07:55AM (#43935804)
Are any of the runtimes already implementing this?
Re:WASM 2.0 by adrian17 on Friday May 09, 2025 @08:01AM (#43935834)
Most have been for some time now. As the announcement post says:

> the Wasm Community and Working Groups had reached consensus and finished the specification in early 2022. All major implementations have been shipping 2.0 for even longer.

> In a future post we will take a look at Wasm 3.0, which is already around the corner at this point!

Features in 3.0 presumably also being mostly implemented already, some maybe just kept behind feature flags.

Re:WASM 2.0 by titzer on Friday May 09, 2025 @08:48AM (#43936143)
Everything in 3.0 has at least two browser implementations; that's part of the requirements for advancement to phase 4.

Wasm 2.0 is complete in a handful of engines, whereas 3.0 is less well-supported.

Wizard is almost done with 3.0; only memory64 and relaxed-simd are incomplete.

Re:WASM 2.0 by thrance on Friday May 09, 2025 @09:43AM (#43936658)
Is there anywhere I could look at the "changelogs" between 1.0 and 2.0, and 2.0 and 3.0? All I could find are different versions of the spec that don't seem very keen on expliciting what changed.
Re:WASM 2.0 by thomasballinger on Friday May 09, 2025 @11:28AM (#43937906)
Re:WASM 2.0 by thrance on Friday May 09, 2025 @01:58PM (#43939483)
Many thanks!