If I were to stream… and it was mostly just me doing my day to day work, while talking to chat, would anyone watch? Setup isn’t going to be anything stellar, no real agenda - I’d pretty much just go do stuff across 5 or 6 repos in parallel & talk through what I’m thinking
you can fork a live os too, i was thinking that agent could attach its vm state for every thing it does or every ticket, has a already running server you can preview when you click it so other agents can pull it down or branch off that hot machine. Currently yes vmstate is captureing the memory snapshot of the OS and thats what we are restoring, how we are able to run pnpm test, then 5 tests in, move it to another compute note, and test 6 starts getting processed etc.
Using module federation to move code to machines closer to databases on the fly instead of making queries across regions. In this case im using "compute federation" send a service to bare metal where the DB is, query the DB, then capture the vm state and restore that VM state back to another region.
@ReedHarmeyer Only constraint is the chip architecture needs to be the same. So I can go from raspberry pi to M series Mac to aws ARM server. But cannot shift between x86 and ARM, can do x86 to x86 tho
import {doSomething} from 'java_machine/dbActions"
Then i have a runtime plugin and bindgen that converts services into expose module bindings. So you literally import the java machine + the vm state, and restore it, exactly where it was, mid event loop, so startup is very fast because it never stopped running.