Andrea Giammarchi

@jorroll > Curious where MDN claims otherwise? First paragraph: https://developer.mozilla.org/en-US/docs/Web/API/SharedWorker  > In [Comms](https://comms.day/) we use the Web Lock's API to accomplish this. Interesting, never tried that...

@jorroll > And as you note, if the database can fit in memory, there are also projects out there which will persist it to indexeddb and just load the whole...

@jorroll coincident erase that complexity … I can drive both main and node or bun from a never blocking worker and it works fine even with UI only libraries. Of...

@nickchomey the question remains: what would be a concrete use case for that? a shared worker has many tabs/windows' ports attached ... what would a roundtrip from a SharedWorker SAB...

@brianblakely thanks! but my question, or maybe ignorance, remains ... a *SharedArrayBuffer* is a reference that passes forward and receives back its integrity (data speaking) ... accordingly, are we saying...

I stand corrected then (TIL) … I still need to understand what could be a use case, or better, I see the possibility to circumvent lock API though a shared...

not sure I am adding anything, but *IDs* have a meaning in *SVG* namespaces too where these can be embedded into the document and conflict with outer *IDs* without having...

FWIWI I fully agree with @sorvell ... the whole point of this proposal was to simplify DOM manipulation, not to complicate it even further with tons of repeated checks or...

> it might be weird if moveBefore() sometimes had huge side effects like running script, initializing iframes, applying styles, etc., yet other times no side effects at all (because the...

to whom it might concern, because we drive DOM synchronously from Workers and WASM interpreters we ended up [solving this issue in a similar way](https://github.com/WebReflection/coincident/blob/main/src/window/events.js), although we used just an...