{"id":143780,"date":"2025-09-18T11:11:56","date_gmt":"2025-09-18T09:11:56","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/opublikovan-standart-webassembly-3-0"},"modified":"2025-09-18T11:11:56","modified_gmt":"2025-09-18T09:11:56","slug":"opublikovan-standart-webassembly-3-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/opublikovan-standart-webassembly-3-0","title":{"rendered":"The WebAssembly 3.0 standard has been published","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The W3C consortium has announced the readiness of a specification standardizing the WebAssembly 3.0 intermediate code and its associated API, which allows for the creation of high-performance applications that are portable across browsers and hardware platforms. WebAssembly provides a browser-independent universal low-level intermediate code for executing applications compiled from various programming languages. <\/p>\n
The WebAssembly technology can be utilized in the browser for tasks that require high performance, such as video encoding, audio processing, graphics manipulation, 3D, game development, cryptographic operations, and mathematical calculations by enabling the execution in the browser of code written in compiled languages like C\/C++. By utilizing JIT for WebAssembly, performance levels close to native code can be achieved. <\/p>\n
Among the main tasks of WebAssembly are ensuring portability, predictability of behavior, and identity of code execution across different platforms. WebAssembly is not limited to browsers and is also promoted as a universal platform for secure execution of code in any infrastructure, operating systems, and devices. <\/p>\n
The following specifications are available: <\/p>\n
\n
WebAssembly Core \u2014 describes a low-level virtual machine for executing WebAssembly intermediate code. Resources related to WebAssembly are supplied in the format \u2018.wasm\u2019, similar to \u2018.class\u2019 files in Java, and contain static data and code segments for working with that data. <\/li>\n
WebAssembly JavaScript API \u2014 provides an API for integration with JavaScript. It allows for obtaining values and passing parameters to WebAssembly functions. The execution of WebAssembly adheres to JavaScript's security model, and all interactions with the host system are analogous to executing JavaScript code.\n
WebAssembly Web API \u2014 defines a programming interface based on the Promise mechanism for requesting and executing \u2018.wasm\u2019 resources. The format of WebAssembly resources is optimized for immediate execution, without waiting for the complete loading of the file, which improves the responsiveness of web applications.\n
WASI API \u2014 defines a modular system interface for running WebAssembly outside of browsers and provides access to resources such as files, network connections, pseudo-random number generators, and system clocks. <\/ul>\n
It is noted that the new version of the standard significantly improves support for compiling high-level languages to WebAssembly. For example, the ability to compile projects in languages such as Java, OCaml, Scala, Kotlin, Scheme, and Dart into WebAssembly has been implemented. Key changes in WebAssembly 3.0, compared to the second version of the standard: <\/p>\n
\n
Support for a 64-bit address space has been implemented. The i64 type can now be used for memory addressing, rather than only i32, which expands the addressable space for applications from 4 GB to 16 EB (with a limit of 16 GB when running in a browser).\n
The ability to use multiple memory objects simultaneously in a single WebAssembly module and to work with different address spaces has been provided. Among other things, it is possible to copy data between different instances of memory objects located in different address spaces.\n
Support for garbage collection has been added. In addition to the previously available linear memory, a separate type of storage that is automatically managed by a garbage collector has been introduced. The compiler can now use separate data structures, arrays, and variables, for which WebAssembly is responsible for memory allocation and lifecycle management.\n
Support for typed references has been added, which can describe the exact structure of the value to which the reference points, allowing for the avoidance of additional runtime checks. Subtypes, type recursion, and the safe use of function references that do not require type and boundary checks at runtime are supported.\n
Support for tail calls has been added, where the current function immediately completes execution after calling another function, without consuming stack space.\n
Support for exception handling has been added.\n
Support for \u2018relaxed\u2019 vector SIMD instructions has been added, allowing for higher performance by relaxing strict semantic adherence across all hardware platforms.\n
Support has been added for a deterministic execution profile that defines platform-independent behavior for instructions whose execution results may differ across platforms (floating-point operations, returning NaN, weakened vector instructions). When this profile is selected, Wasm ensures deterministic behavior, reproducibility, and portability.\n
A syntax for creating custom annotations has been added, allowing additional information to be attached to WebAssembly code. Previously, support for custom sections that store arbitrary information existed in the binary format of WebAssembly, but was missing in the textual format. Now, there is the possibility to add this information in a readable and editable format.\n
Built-in functions for working with strings have been added to the JavaScript API. Previously, JavaScript strings could only be passed to WebAssembly as external references, but now they can be directly accessed and manipulated within WebAssembly. <\/ul>\n