Episode 105: Reaction: Progrium Technology Thesis

We learn more about the philosophy behind WANIX and react to the thesis video from its creator @progrium.

With a big emphasis on reusable/extensible building blocks, WANIX and the broader Tractor ecosystem seem to dovetail well with our WASM-based agent plugin system. Can we use this for AutoDevs?

- Original video & transcript: https://progrium.com/blog/progrium-technology-thesis/

- Progrium github: github.com/progrium

- Tractor github: github.com/tractordev

- WANIX site: wanix.sh

- WANIX github: github.com/tractordev/wanix

https://x.com/openagentsinc/status/1805320338064261219?s=46

Reply to this note

Please Login to reply.

Discussion

I'm curious what you find special or unique about WANIX? At first glance it looks like a lot of arbitrary decisions made for a computing environment building block without much explanation as to why it's better than alternatives

Mostly excited about WANIX as basis for an agent runtime because it enables agents to run local-first in a browser while enabling 1) read/write access to filesystems including GitHub, 2) compilation of new Go programs in the browser (because the Go compiler is shipped to the browser via WASM), 3) an in-browser dev pipeline for webapps and binaries, and 4) usage of our existing agent plugins also using WASM

tl;dr WANIX has all the building blocks needed for agentic recursive self-improvement