T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README prose a little bit (#4762)

Browse Source
This commit is contained in:
Nick Fitzgerald
2022-08-23 13:41:59 -07:00
committed by GitHub
parent b5f1ab7780
commit cb918e8a24
1 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@@ -64,25 +64,25 @@ Hello, world!
* **Fast**. Wasmtime is built on the optimizing [Cranelift] code generator to * **Fast**. Wasmtime is built on the optimizing [Cranelift] code generator to
quickly generate high-quality machine code either at runtime or quickly generate high-quality machine code either at runtime or
ahead-of-time. Wasmtime's runtime is also optimized for cases such as ahead-of-time. Wasmtime is optimized for efficient instantiation, low-overhead
efficient instantiation, low-overhead transitions between the embedder and calls between the embedder and wasm, and scalability of concurrent instances.
wasm, and scalability of concurrent instances.
* **[Secure]**. Wasmtime's development is strongly focused on the correctness of * **[Secure]**. Wasmtime's development is strongly focused on correctness and
its implementation with 24/7 fuzzing donated by [Google's OSS Fuzz], security. Building on top of Rust's runtime safety guarantees, each Wasmtime
leveraging Rust's API and runtime safety guarantees, careful design of feature goes through careful review and consideration via an [RFC
features and APIs through an [RFC process], a [security policy] in place process]. Once features are designed and implemented, they undergo 24/7
for when things go wrong, and a [release policy] for patching older versions fuzzing donated by [Google's OSS Fuzz]. As features stabilize they become part
as well. We follow best practices for defense-in-depth and known of a [release][release policy], and when things go wrong we have a
protections and mitigations for issues like Spectre. Finally, we're working well-defined [security policy] in place to quickly mitigate and patch any
to push the state-of-the-art by collaborating with academic issues. We follow best practices for defense-in-depth and integrate
researchers to formally verify critical parts of Wasmtime and Cranelift. protections and mitigations for issues like Spectre. Finally, we're working to
push the state-of-the-art by collaborating with academic researchers to
formally verify critical parts of Wasmtime and Cranelift.
* **[Configurable]**. Wastime supports a rich set of APIs and build time * **[Configurable]**. Wasmtime uses sensible defaults, but can also be
configuration to provide many options such as further means of restricting configured to provide more fine-grained control over things like CPU and
WebAssembly beyond its basic guarantees such as its CPU and Memory memory consumption. Whether you want to run Wasmtime in a tiny environment or
consumption. Wasmtime also runs in tiny environments all the way up to massive on massive servers with many concurrent instances, we've got you covered.
servers with many concurrent instances.
* **[WASI]**. Wasmtime supports a rich set of APIs for interacting with the host * **[WASI]**. Wasmtime supports a rich set of APIs for interacting with the host
environment through the [WASI standard](https://wasi.dev). environment through the [WASI standard](https://wasi.dev).