@schmoo2k.bsky.social
Software Architect currently fixating on WebAssembly, unikernels and novel approaches to interoperability.
I do embeddings not at the edge, but at the client (even better for the use case) using llama.cpp (in webassembly), it downloads the bge-base-en-v1.5-gguf embedding model as needed as well as a pre-calculated vector db (small enough to be to be in memory).
October 25, 2025 at 3:13 PM
I do embeddings not at the edge, but at the client (even better for the use case) using llama.cpp (in webassembly), it downloads the bge-base-en-v1.5-gguf embedding model as needed as well as a pre-calculated vector db (small enough to be to be in memory).
Something like: github.com/microsoft/wa...
GitHub - microsoft/wassette: Wassette: A security-oriented runtime that runs WebAssembly Components via MCP
Wassette: A security-oriented runtime that runs WebAssembly Components via MCP - microsoft/wassette
github.com
October 21, 2025 at 4:48 PM
Something like: github.com/microsoft/wa...
I feel your pain - but if you have worked in the cross-compiler world (developing for platform X on platform Y) you will recognise a lot of those pain points and appreciate the "why" it is painful... IMO there is a critical mass now and you only need to look at all the "where" places it can be run!
September 25, 2025 at 6:21 PM
I feel your pain - but if you have worked in the cross-compiler world (developing for platform X on platform Y) you will recognise a lot of those pain points and appreciate the "why" it is painful... IMO there is a critical mass now and you only need to look at all the "where" places it can be run!
When you say "the other one", I assume you mean another wasm module? If so, one wasm module, can't load another. But a single host can load two wasm modules and resolve their "imports" between them.
May 29, 2025 at 5:37 PM
When you say "the other one", I assume you mean another wasm module? If so, one wasm module, can't load another. But a single host can load two wasm modules and resolve their "imports" between them.
Ok, I will bite - what issues with WASI preview 3?
May 26, 2025 at 6:34 PM
Ok, I will bite - what issues with WASI preview 3?
I use spin + vitepress for such things. Here is a boilerplate repo: github.com/GordonSmith/... and generated site: vitepress.fermyon.app
GitHub - GordonSmith/spin-vitepress: Vitepress + Spin
Vitepress + Spin. Contribute to GordonSmith/spin-vitepress development by creating an account on GitHub.
github.com
April 30, 2025 at 6:50 PM
I use spin + vitepress for such things. Here is a boilerplate repo: github.com/GordonSmith/... and generated site: vitepress.fermyon.app
Any word on data accelerators being replaced with Hyperlight and Wasm?
learn.microsoft.com/en-us/azure/...
learn.microsoft.com/en-us/azure/...
Azure Data Lake Storage query acceleration - Azure Storage
Query acceleration enables applications and analytics frameworks to dramatically optimize data processing by retrieving only the data that is required for a processing operation.
learn.microsoft.com
April 26, 2025 at 10:58 AM
Any word on data accelerators being replaced with Hyperlight and Wasm?
learn.microsoft.com/en-us/azure/...
learn.microsoft.com/en-us/azure/...
You may get better stack info, if you enable DWARF?
April 22, 2025 at 4:54 PM
You may get better stack info, if you enable DWARF?
I use the VitePress doc generator and it uses TextMate grammars via Shikira (from memory).
January 3, 2025 at 2:33 PM
I use the VitePress doc generator and it uses TextMate grammars via Shikira (from memory).
It does doesn't it!
But there is one significant difference: Java / JVM has full access to the host machine by default, while WebAssembly has zero access to the host machine by default...
But there is one significant difference: Java / JVM has full access to the host machine by default, while WebAssembly has zero access to the host machine by default...
December 3, 2024 at 8:56 PM
It does doesn't it!
But there is one significant difference: Java / JVM has full access to the host machine by default, while WebAssembly has zero access to the host machine by default...
But there is one significant difference: Java / JVM has full access to the host machine by default, while WebAssembly has zero access to the host machine by default...
I would recommend taking a look at "spin" from fermyon: www.fermyon.com/spin
Develop serverless WebAssembly apps with Spin
Develop serverless WebAssembly apps with Spin
www.fermyon.com
November 21, 2024 at 10:28 AM
I would recommend taking a look at "spin" from fermyon: www.fermyon.com/spin
Ensure you using a fast host (wamr, wasmtime etc), then you do an AOT compile for that host.
The other trick in the bag is to use github.com/bytecodealli... which lets you pre-run your wasm module up to a defined point and snapshots at that point, ideal for pre-initializing runtimes etc.
The other trick in the bag is to use github.com/bytecodealli... which lets you pre-run your wasm module up to a defined point and snapshots at that point, ideal for pre-initializing runtimes etc.
November 20, 2024 at 8:51 AM
Ensure you using a fast host (wamr, wasmtime etc), then you do an AOT compile for that host.
The other trick in the bag is to use github.com/bytecodealli... which lets you pre-run your wasm module up to a defined point and snapshots at that point, ideal for pre-initializing runtimes etc.
The other trick in the bag is to use github.com/bytecodealli... which lets you pre-run your wasm module up to a defined point and snapshots at that point, ideal for pre-initializing runtimes etc.
Shamless plug - There is a vscode extension which wraps all this up into a notebook enivironment: marketplace.visualstudio.com/items?itemNa...
It also has an `export to html` option to host in a single page...
It also has an `export to html` option to host in a single page...
November 20, 2024 at 8:42 AM
Shamless plug - There is a vscode extension which wraps all this up into a notebook enivironment: marketplace.visualstudio.com/items?itemNa...
It also has an `export to html` option to host in a single page...
It also has an `export to html` option to host in a single page...
I think you are missing the "why" of the hype.
If you limit your world view to hosts that can already run JS/TS natively then you are correct.
But given WASM can also execute in so many places outside of browser engines and since Rust treats WASM as a first-class target, the hype train isn't over.
If you limit your world view to hosts that can already run JS/TS natively then you are correct.
But given WASM can also execute in so many places outside of browser engines and since Rust treats WASM as a first-class target, the hype train isn't over.
November 18, 2024 at 11:40 AM
I think you are missing the "why" of the hype.
If you limit your world view to hosts that can already run JS/TS natively then you are correct.
But given WASM can also execute in so many places outside of browser engines and since Rust treats WASM as a first-class target, the hype train isn't over.
If you limit your world view to hosts that can already run JS/TS natively then you are correct.
But given WASM can also execute in so many places outside of browser engines and since Rust treats WASM as a first-class target, the hype train isn't over.