{"id":100537,"date":"2021-06-18T16:22:49","date_gmt":"2021-06-18T14:22:51","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/dostupen-wasmer-2-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly"},"modified":"2021-06-18T16:22:49","modified_gmt":"2021-06-18T14:22:51","slug":"dostupen-wasmer-2-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/dostupen-wasmer-2-0-instrumentarij-dlya-sozdaniya-prilozhenij-na-baze-webassembly","title":{"rendered":"Wasmer 2.0 is now available, a toolkit for creating applications based on WebAssembly.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The second major release of the Wasmer project has occurred, developing a runtime for executing WebAssembly modules that can be used to create universal applications capable of running across 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

Portability is ensured through the compilation of application code into low-level WebAssembly bytecode, which can run on any OS or be embedded in programs written in other programming languages. Programs are lightweight containers in which WebAssembly pseudocode is executed. 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 compiling to WebAssembly. Various compilation backends (Singlepass, Cranelift, LLVM) and engines (utilizing JIT or generating machine code) are supported for translating WebAssembly to the machine code of the current platform. <\/p>\n

Access management and interaction with the system is provided through the WASI API (WebAssembly System Interface), which offers programming interfaces for working with files, sockets, and other functions provided by the operating system. Applications are isolated from the main system in a sandbox environment and have access only to the declared functionality (the security mechanism is based on capability management \u2014 the application must be granted corresponding permissions to perform actions on each of the resources (files, directories, sockets, system calls, etc.)). <\/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

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

The significant version change of Wasmer is associated with introducing breaking changes to the internal API, which, according to the developers, will not affect 99% of the platform's users. Additionally, the breaking changes include a modification to the format of serialized Wasm modules (modules serialized in Wasmer 1.0 will not be usable in Wasmer 2.0). Other changes: <\/p>\n