#OpenDoors #ThisIsOpenDoors #AlternativeRock #Gitarrist #Bassist
#OpenDoors #ThisIsOpenDoors #AlternativeRock #Gitarrist #Bassist
#OpenDoors #ThisIsOpenDoors #AlternativeRock #Schlagzeuger #Bassist
#OpenDoors #ThisIsOpenDoors #AlternativeRock #Schlagzeuger #Bassist
Components model is terrible and wasix always a mystery to me.
Components model is terrible and wasix always a mystery to me.
#Papírnictví #Papír #Japonsko #WašiPapír
#Papírnictví #Papír #Japonsko #WašiPapír
The incredible power of trial, observation & (sometimes) writing stuff down predates the modern scientific era!
The incredible power of trial, observation & (sometimes) writing stuff down predates the modern scientific era!
A WebAssembly runtime written in Erlang, without a native Wasm engine.
Now with WASI 0.3, component snapshots and faster compiled execution. Built for running plugins and AI-generated code with isolation and OTP supervision.
github.com/benoitc/erla...
A WebAssembly runtime written in Erlang, without a native Wasm engine.
Now with WASI 0.3, component snapshots and faster compiled execution. Built for running plugins and AI-generated code with isolation and OTP supervision.
github.com/benoitc/erla...
📊 6.3/10
🏢 bytecodealliance
📝 The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can s...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-125159
#cybersecurity #infosec #cve #euvd
📊 6.3/10
🏢 bytecodealliance
📝 The wasmtime-wasi-http p2 implementation in Wasmtime before 36.0.20, 37.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 can s...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-125159
#cybersecurity #infosec #cve #euvd
📊 5.3/10
🏢 bytecodealliance
📝 Wasmtime's wasmtime-wasi crate 48.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 contains a time-of-check/time-of-use race i...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-125033
#cybersecurity #infosec #cve #euvd
📊 5.3/10
🏢 bytecodealliance
📝 Wasmtime's wasmtime-wasi crate 48.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 contains a time-of-check/time-of-use race i...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-125033
#cybersecurity #infosec #cve #euvd
Cooking something with wasm components and rust right now, and damn it feels good.
This bigger-than-usual Rust release adds the never type (`!`), the Allocator api, DropGuard, Box::map, Vec::from_fn, and more! Cargo now warns for unused dependencies, rebuilds less often, and adds the min-publish-age setting!
blog.rust-lang.org/2026/11/12/R...
Cooking something with wasm components and rust right now, and damn it feels good.
atproto-bench now has a build matrix: one lil probe per sdk (resolve a DID, read record over HTTPS), cross-compiled for 11 targets
sdk lineup: zat, indigo, atmos, jacquard, rsky and atproto/api.
each cell below names the libc the binary links
atproto-bench now has a build matrix: one lil probe per sdk (resolve a DID, read record over HTTPS), cross-compiled for 11 targets
sdk lineup: zat, indigo, atmos, jacquard, rsky and atproto/api.
each cell below names the libc the binary links
from what i seen i like the WASI for userspace (irrespective of WASM, it's a modern capability based system interface)
it could use some io_uring async no-syscall interface for super high bandwidth tasks, but for run-of-the-mill software it's getting there
from what i seen i like the WASI for userspace (irrespective of WASM, it's a modern capability based system interface)
it could use some io_uring async no-syscall interface for super high bandwidth tasks, but for run-of-the-mill software it's getting there