Sébastien DeleuzeBreaking news : the Kotlin/Wasm team has just shared the very first incarnation of their server-side wasi-http support based on the Wasm Component Model. https://github.com/Kotlin/sample-wasi-http-kotlin/
ARGVMI~1.PIFI wonder if there is an #SSG (static site generator) that can be extended with WASI modules.
Kinda like how you can extend #11ty with JavaScript code, except it doesn't care what language you use as long as it compiles to #WASI.
Native executables would work too (that's what GIMP plugins are), but they aren't cross-platform, and #webdev tools are generally expected to run on any platform without manually installing toolchains and compiling, so WASI seems like a reasonable solution.
Brett CannonBased on https://github.com/pydantic/monty?tab=readme-ov-file#pyodide , if I can make #Python under #WASI a winner if I make start-up faster via https://github.com/bytecodealliance/wasmtime/tree/main/crates/wizer , get more 3rd-party C libraries working (e.g. zlib), and make it easy to slim down the file size.
Inautilo#Development #Overviews
The State of WebAssembly 2025/2026 · ”Wasm is no longer an experiment, it’s ready for production.” https://ilo.im/16a17n
_____
#Programming #WebAssembly #WASM #WASI #ESM #JavaScript #Browser #WebDev #Frontend #Backend
Alvin Ashcraft 🐿️The State of WebAssembly – 2025 and 2026
https://platform.uno/blog/the-state-of-webassembly-2025-2026/
🫧 socialcoding..#WASM / #WASI based #plugin architectures vs #AGPL?
I assume this is valid, but #IANAL and unsure if it is indeed the case:
- If the core system is AGPL-licensed and integrates a Wasm WASI runtime.
- Then 3rd-party WASI Components can have different licenses.
- Esp. when they are downloaded and installed at run-time.
OTOH perhaps not.. and it depends on who designed the #WIT #RPC interface, and what its #license is.
#Socialcoding topic (2024, all fedi links rotted)..
https://discuss.coding.social/t/sx-licensing-of-plugin-architecture-vs-agpl/506
SX: Licensing of Plugin Architecture vs. AGPL?
In our plans for the AGPL-licensed tool suite there are a range of extensibility points, and a plugin architecture that facilitates 3rd-party service integration. We should know in detail the various licensing aspects to take into account for each of these. On one hand we want as much as possible to be AGPL-licensed, enriching the ecosystem. While for 3rd-party services we want to leave the option open to publish them for integration under different licenses. On the Fedi I posed the following ...
GitRootWhat about plugins in GitRoot? They are essential. Without them, you just have #Git repositories; with them, you get a full-featured #forge.
Currently, plugins are #wasm binaries following the #wasi specification. They can read/write to your Git repository and web space (files in a directory).
They are triggered on every push diff, depending on your `.gitroot/plugins.yml` configuration. More on plugin rights: https://gitroot.dev/doc/how-tos/plugin_rights.html
1/3
Currently, plugins are #wasm binaries following the #wasi specification. They can read/write to your Git repository and web space (files in a directory).
They are triggered on every push diff, depending on your `.gitroot/plugins.yml` configuration. More on plugin rights: https://gitroot.dev/doc/how-tos/plugin_rights.html
1/3
some kind of orange shapeIt's going to get a lot easier to run #Lisien in the browser with the next release. It won't be the most performant way to do it, probably, and for the time being you'll need to use XML dumps of the database for persistence, though I've heard of ways to avoid that.
#Python #WASI lazyweb: is there a good, pure Python library I could use to store cookies? I guess I could compile SQLite in, if I have to, but it seems like needless overhead.
Today, GitRoot plugins can be written in Golang thanks to @TinyGo and in TypeScript thanks to https://www.assemblyscript.org/
Guess what the next SDK plugin will be made of.
#golang #tinygo #typescript #assemblyscript #wasm #wasi
Guess what the next SDK plugin will be made of.
#golang #tinygo #typescript #assemblyscript #wasm #wasi
Thomas Steiner 
It's all still experimental and not super tightly sandbox secure yet, but #WASI support in Node.js is very much a thing: https://nodejs.org/api/wasi.html. #TIL 🤯 #Wasm #WebAssembly