druid VS wasi-libc

d:\github\rust\lapce>cargo build Updating git repository `https://github.com/lapce/druid` Updating git repository `https://github.com/lapce/xi-editor` Updating git submodule `https://github.com/xi-editor/syntect-resources` Updating git repository `https://github.com/lapce/piet-wgpu` Downloaded Inflector v0.11.4 Downloaded alacritty_terminal v0.15.0 Downloaded addr2line v0.16.0 Downloaded ansi_term v0.12.1 Downloaded bit-vec v0.6.3 Downloaded arrayvec v0.4.12 Downloaded bitmaps v2.1.0 Downloaded byteorder v1.4.3 Downloaded copypasta v0.7.1 Downloaded bit-vec v0.5.1 Downloaded crossbeam v0.7.3 Downloaded crossbeam-epoch v0.8.2 Downloaded crossbeam-utils v0.7.2 Downloaded darling_macro v0.13.1 Downloaded darling_core v0.13.1 Downloaded filetime v0.2.15 Downloaded foreign-types-shared v0.1.1 Downloaded form_urlencoded v1.0.1 Downloaded futures-util v0.3.17 Downloaded futures-task v0.3.17 Downloaded futures-macro v0.3.17 Downloaded h2 v0.3.9 Downloaded fixedbitset v0.2.0 Downloaded indexmap v1.7.0 Downloaded git2 v0.13.23 Downloaded khronos-egl v4.1.0 Downloaded kurbo v0.8.1 Downloaded lsp-types v0.89.2 Downloaded libssh2-sys v0.2.21 Downloaded memmap2 v0.5.0 Downloaded mio-anonymous-pipes v0.2.0 Downloaded nodrop v0.1.14 Downloaded memchr v2.4.1 Downloaded object v0.26.2 Downloaded pin-utils v0.1.0 Downloaded ndarray v0.11.2 Downloaded proc-macro-nested v0.1.7 Downloaded rand_chacha v0.1.1 Downloaded proc-macro2 v1.0.29 Downloaded rand_isaac v0.1.1 Downloaded rand_jitter v0.1.4 Downloaded rustc_version v0.2.3 Downloaded rustc-demangle v0.1.21 Downloaded scopeguard v1.1.0 Downloaded seahash v4.1.0 Downloaded sharded-slab v0.1.3 Downloaded serde_json v1.0.67 Downloaded smallvec v1.6.1 Downloaded svgtypes v0.5.0 Downloaded strum_macros v0.19.4 Downloaded syn v1.0.75 Downloaded time-macros v0.1.1 Downloaded tinyfiledialogs v3.8.3 Downloaded tracing-core v0.1.19 Downloaded unic-langid v0.9.0 Downloaded ucd-trie v0.1.3 Downloaded unicode-script v0.5.3 Downloaded unicode-segmentation v1.8.0 Downloaded vte_generate_state_changes v0.1.1 Downloaded want v0.3.0 Downloaded wasmer-vm v2.1.1 Downloaded wasmer-wasi v2.1.1 Downloaded winreg v0.7.0 Downloaded wio v0.2.2 Downloaded yaml-rust v0.4.5 Downloaded ahash v0.4.7 Downloaded bincode v1.3.3 Downloaded cc v1.0.69 Downloaded xi-rope v0.3.0 Downloaded cranelift-codegen v0.76.0 Downloaded crossbeam-deque v0.8.1 Downloaded crossbeam-channel v0.2.6 Downloaded enumset_derive v0.5.5 Downloaded fluent-bundle v0.15.1 Downloaded futures-io v0.3.17 Downloaded generic-array v0.14.4 Downloaded data-url v0.1.0 Downloaded hyper v0.14.16 Downloaded gimli v0.25.0 Downloaded ident_case v1.0.1 Downloaded intl_pluralrules v7.0.1 Downloaded iovec v0.1.4 Downloaded lazy-bytes-cast v5.0.1 Downloaded lazy_static v0.2.11 Downloaded lyon v0.17.5 Downloaded memoffset v0.2.1 Downloaded memoffset v0.5.6 Downloaded num_cpus v1.13.1 Downloaded libz-sys v1.1.3 Downloaded naga v0.7.1 Downloaded parking_lot v0.6.4 Downloaded pico-args v0.4.2 Downloaded proc-macro-error-attr v1.0.4 Downloaded petgraph v0.6.0 Downloaded rand_xoshiro v0.4.0 Downloaded rand_xorshift v0.1.1 Downloaded rayon v1.5.1 Downloaded rustversion v1.0.6 Downloaded regalloc v0.0.31 Downloaded serde_bytes v0.11.5 Downloaded rustybuzz v0.3.0 Downloaded sized-chunks v0.6.5 Downloaded sled v0.34.7 Downloaded static_assertions v1.1.0 Downloaded try-lock v0.2.3 Downloaded tower-service v0.3.1 Downloaded unic-bidi v0.9.0 Downloaded ttf-parser v0.12.3 Downloaded unicode-bidi-mirroring v0.1.0 Downloaded vte v0.10.1 Downloaded uuid v0.7.4 Downloaded wasmer-object v2.1.1 Downloaded wasmer-engine-universal v2.1.1 Downloaded which v4.2.2 Downloaded ahash v0.7.6 Downloaded arrayvec v0.5.2 Downloaded bytemuck v1.7.2 Downloaded bytes v1.1.0 Downloaded xi-rpc v0.3.0 Downloaded console v0.6.2 Downloaded crossbeam-deque v0.5.2 Downloaded digest v0.9.0 Downloaded darling v0.13.1 Downloaded crossbeam v0.4.1 Downloaded glob v0.3.0 Downloaded heck v0.3.3 Downloaded float-cmp v0.5.3 Downloaded hashbrown v0.11.2 Downloaded itoa v0.4.8 Downloaded line-wrap v0.1.1 Downloaded lazycell v1.3.0 Downloaded loupe-derive v0.1.3 Downloaded jobserver v0.1.24 Downloaded memoffset v0.6.4 Downloaded ipnet v2.3.1 Downloaded mime v0.3.16 Downloaded native-tls v0.2.8 Downloaded parking_lot v0.11.2 Downloaded pathfinder_geometry v0.5.1 Downloaded libc v0.2.101 Downloaded proc-macro-hack v0.5.19 Downloaded rand v0.8.4 Downloaded piet v0.4.0 Downloaded rustc-hash v1.1.0 Downloaded schannel v0.1.19 Downloaded roxmltree v0.14.1 Downloaded serde v0.8.23 Downloaded strum v0.19.5 Downloaded time v0.1.43 Downloaded thiserror-impl v1.0.28 Downloaded tracing-attributes v0.1.15 Downloaded serde v1.0.130 Downloaded unic-char-property v0.9.0 Downloaded tree-sitter v0.19.2 Downloaded petgraph v0.5.1 Downloaded tokio v1.15.0 Downloaded vcpkg v0.2.15 Downloaded wasmer-engine-dylib v2.1.1 Downloaded copyless v0.1.5 .... Downloaded 415 crates (29.2 MB) in 1m 13s (largest was `profiling` at 1.7 MB) ....

It uses a forked version of Druid. https://github.com/lapce/druid which replaces the window management to use winit instead https://github.com/rust-windowing/winit

Now there are projects like WASI that allows for interfacing with system resources for WASM code this allows for devs to target WASM runtime for their apps sliding the apps to run locally on any OS without any porting required. This could be a game changer in the future like Docker and containers was in the past decade.

So it doesn’t seem like there has been progress on a pseudo-random number generator function for typst, but there are multiple other ways to solve this: 1. Just don’t. Typst has this functional philosophy, there one input always produces the same output. (not an answer to your question tho) 2. Interface with a webassembly module which has a random number generator. So you could e.g. compile c to wasm and statically link a libc version. You would then just have to export the rand() function. (You could use any lang for this, which has a stdlib with a pseudo random number generator) 3. Implement your own. Random number generators are actually not that hard something like an LCG isn’t to complex. (Id provide an example but im on my phone rn)

Actually WASI[0] will be a better alternative, IIRC extism serialize and deserialize the data that you want to pass every time, adding a lot of overhead.

[0] https://wasi.dev

Actually, it was in wasi-libc: https://github.com/WebAssembly/wasi-libc/blob/main/libc-bott...

Proper isolation in C# is only now becoming a thing, with .Net support for WASI, which is essentially a WebAssembly sandbox which can be given extremely granular privileges (such as access to spefic file system directories, or an effective virtual file system). As an upside, the idea is that it should be possible to write the WASI packages in more or less anything.

Wasm Labs dev here :)

In mod_wasm, there are some differences with a pure CGI implementation. When Apache boots, it loads the configuration and initializes the WasmVM. When a new HTTP request arrives, the VM is ready so you don't need to initialize a different process to manage it.

You still need to process the request and pass the data to the Wasm module. This step is done via STDIN through the WebAssembly System Interface (WASI) implementation [0]. The same happens in the opposite direction, as the module returns the data via STDOUT.

So, the CGI pattern is still there, but it doesn't require new processes and all the code runs in a sandbox.

However this is not the only way you can run a Wasm module. In this specific case, we use CGI via WASI. In other cases, you may compile a module to fulfill a specific API, like ProxyWasm [1] to create HTTP filters for proxies like Envoy.

- [0] https://wasi.dev/

- [1] https://github.com/proxy-wasm/spec

Never done that, but I think you need this: https://wasi.dev/

The Python builds from the WebAssembly language runtimes [0] project target the WebAssembly System Interfaces (WASI) [1]. It allows the Python interpreter to interact with resources like the filesystem.

Many server-side Wasm runtimes supports WASI out of the box. For the browser, you need to provide a polyfill to emulate these resources like the one provided by the WASI team [2].

Regarding SQLite, these builds include libsqlite so you should be able to use it :)

- [0] https://github.com/vmware-labs/webassembly-language-runtimes

- [1] https://wasi.dev/

- [2] https://wasi.dev/polyfill/

Effective debugging results in effective programming; itk-wasm makes effective debugging of WebAssembly possible. In this tutorial, adapted from the itk-wasm documentation, we walk through how to debug a C++ data processing pipeline with the mature, native binary debugging tools that are comfortable for developers. This is a fully featured way to ensure the base correctness of a processing pipeline. Next, we will walk through an interactive debugging experience for WASI WebAssembly. With itk-wasm, we can debug the same source code in either context with an interactive debugger. We also have a convenvient way to pass data from our local filesystem into a WebAssembly (Wasm) processing pipeline.

Communication between the WASM module and the rest of the application needs to be done in very simple types (bytes, ints and floats). No complex types are supported yet. This is why most WASM compilers also provide some glue-code to map between complex types like strings or arrays. The Web Assembly System Interface (WAS) is an on-progress standard aimed to solve this last limitation; once it's mature it will allow easy interoperation with almost every environment. WASI is already available in some WSAM compilers and runtimes.