Curious what part you are referring to with the rigid separation. Do you mean the transport layer? for https://t.co/8FTKZKOQh0, i've been using the hidden "in memory" transport in their SDKs and it erases the transport layer. It just makes the calls a local function call.— Benjamin Eckel (@bhelx) March 7, 2025
Transferable objects - Lightning fast | Blog | Chrome for Developers
With transferable objects, data is transferred from one context to another. It is zero-copy, which vastly improves the performance of sending data to a Worker.
Transferable objects - Web APIs | MDN
Transferable objects are objects that own resources that can be transferred from one context to another, ensuring that the resources are only available in one context at a time. Following a transfer, the original object is no longer usable; it no longer points to the transferred resource, and any attempt to read or write the object will throw an exception.
libkrun/libkrun
A dynamic library providing Virtualization-based process isolation capabilities
Linux Internals: How /proc/self/mem writes to unwritable memory - offlinemark
Introduction An obscure quirk of the /proc/*/mem pseudofile is its “punch through” semantics. Writes performed through this file will succeed even if the destination virtual memory is marked unwritable. In fact, this behavior is intentional and actively used by projects such as the Julia JIT comp
Spaces as Layers - Nick's Blog
Public anchor records paired with sidecar records in permissioned spaces give ATProtocol apps a composable pattern for blending open discoverability with controlled access.
Diversity-enabled sweet spots in layered architectures and speed–accuracy trade-offs in sensorimotor control | PNAS
Nervous systems sense, communicate, compute, and actuate movement using distributed components with severe trade-offs in speed, accuracy, sparsity,...
From Lume to Containerization: Our Journey Meets Apple's Vision | Cua Blog
Apple's Containerization framework announcement confirms we're on the right path. Here's what we're looking forward to.
kyju.org
Horribly misusing Rust features to provide provable memory safety and tracing garbage collection for pointer soup.
Boundaries
This talk is about using simple values (as opposed to complex objects) not just for holding data, but also as the boundaries between components and subsystems. It moves through many topics: functional programming; mutability's relationship to OO; isolated unit testing with and without test doubles; and concurrency, to name some. The "Functional Core, Imperative Shell" screencast mentioned at the end is available as part of season 4 of the DAS catalog.
I suspect we’ll see a bunch of apps that leverage atproto’s did:plc identity layer but store data out of band.
boltless
Been tinkering with what cloud functions could look like on AT Proto by storing WASM blobs. Influenced by the IPVM design of my big brain former co-workers from Fission github.com/avivash/at-functions
GitHub - avivash/at-functions
github.comOh this is interesting. At first I thought it was yet another lexicon to wrap data on, but it's a way for anyone to use ATProto as a discovery mechanism for their non-PDS-hosted datasets. I hadn't thought of the ATmosphere and the relays as a way to surface arbitrary existing data until know.
IPFS
🪩 Introducing matadisco.org! — a way to discover open datasets via #atproto that doesn't depend on any single institution staying online. 🕺🏼 We have more public data than ever (satellite imagery, climate models, genomic sequences), but finding it is still painfully hard.
Been tinkering with what cloud functions could look like on AT Proto by storing WASM blobs. Influenced by the IPVM design of my big brain former co-workers from Fission github.com/avivash/at-functions
GitHub - avivash/at-functions
github.com
