{"id":105726,"date":"2022-11-27T09:36:51","date_gmt":"2022-11-27T07:36:51","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/dostupen-wasmer-3-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly"},"modified":"2022-11-27T09:36:51","modified_gmt":"2022-11-27T07:36:51","slug":"dostupen-wasmer-3-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/dostupen-wasmer-3-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly","title":{"rendered":"Wasmer 3.0 is now available, a toolkit for building applications based on WebAssembly.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The third major release of the Wasmer project has been introduced, developing a runtime for executing WebAssembly modules that can be used to create universal applications capable of running on different operating systems, as well as for the isolated execution of untrusted code. The project's code is written in Rust and is distributed under the MIT license. <\/p>\n
The ability to run a single application on different platforms is provided by compiling the code into low-level intermediate WebAssembly code, which can run on any OS or be embedded in programs written in other programming languages. Programs are lightweight containers in which WebAssembly pseudocode executes. These containers are not tied to the operating system and can include code originally written in any programming language. The Emscripten toolkit can be used for compilation to WebAssembly. For translating WebAssembly into machine code for the current platform, different compilation backends (Singlepass, Cranelift, LLVM) and engines (utilizing JIT or generating machine code) are supported. <\/p>\n
Applications are isolated from the main system in a sandbox environment and have access only to the declared functionality (a security mechanism based on capability management \u2014 each resource (files, directories, sockets, system calls, etc.) must be assigned the appropriate permissions for the application to act on it). Access control and interaction with the system are provided through the WASI (WebAssembly System Interface) API, which offers programming interfaces for working with files, sockets, and other functions provided by the operating system. <\/p>\n
The platform enables application execution performance close to that of native builds. Using the Native Object Engine, machine code can be generated for the WebAssembly module (\"wasmer compile \u2014native\" for generating precompiled object files .so, .dylib, and .dll), requiring minimal runtime while retaining all sandbox isolation capabilities. There is an option to supply precompiled programs with the built-in Wasmer. Rust API and Wasm-C-API are offered for building extensions and add-ons. <\/p>\n
To run a WebAssembly container, it is sufficient to install the Wasmer runtime in the system, which comes without external dependencies (\"curl https:\/\/get.wasmer.io -sSfL | sh\"), and run the required file (\"wasmer test.wasm\"). Programs are distributed as regular WebAssembly modules, which can be managed using the WAPM package manager. Wasmer is also available as a library, which can be used to embed WebAssembly code in programs written in Rust, C\/C++, C#, D, Python, JavaScript, Go, PHP, Ruby, Elixir, and Java. <\/p>\n
Key changes in Wasmer 3.0: <\/p>\n
\n
Support for creating native executables for any platform has been added. The command \"wasmer create-exe\" has been completely redesigned to allow the transformation of a file with intermediate WebAssembly code into self-contained executables for Linux, Windows, and macOS platforms that can run without installing Wasmer.\n
Support for running WAPM packages hosted in the wapm.io directory has been provided via the command \"wasmer run\". For example, executing \"wasmer run python\/python\" will load the python package from the wapm.io repository and run it.\n
The Wasmer Rust API has been completely revamped, modifying the memory handling style and allowing for the safe storage of Wasm objects within the Store structure. A new MemoryView structure has been proposed, enabling reading and writing data in a linear memory space.\n
A set of wasmer-js components has been implemented to run Wasmer in a web browser and interact with it from JavaScript, using the wasm-bindgen library. The capabilities of wasmer-js correspond to those of wasmer-sys components, which are designed to run Wasmer on standard operating systems.\n
Engines have been simplified. Instead of separate engines for JIT, dynamic, and static linking (Universal, Dylib, StaticLib), there is now a single unified engine, where code loading and saving are managed at the parameter setup level.\n
The rkyv framework is utilized for deserializing artifacts, operating in zero-copy mode, meaning no additional memory allocation is required, and it performs deserialization using only the originally provided buffer. The application of rkyv has significantly increased launch speed.\n
The Singlepass compiler has been improved, now supporting functions with multiple arguments (multi-value), enhancing reliability and adding support for exception handling frames.\n
The implementation of the WASI (WebAssembly System Interface) API has been improved. Issues in the WASI interface for filesystem operations have been resolved. Internal types have been reworked using WAI (WebAssembly Interfaces), which will enable a series of new capabilities in the future. <\/ul>\n