4 ms·
Well it's BEAM/OTP on Linux presently, but I intend to look at what running a pickled, single-binary on a microkernel might buy me, etc. That said, not using. S
by kgcgfva 13d ago
Well it's BEAM/OTP on Linux presently, but I intend to look at what running a pickled, single-binary on a microkernel might buy me, etc. That said, not using. SeL4 directly.
And, yes, in re: semantic layer, I have't talked bout that part much, yet, but given my experience at Stardog(.com), I've implemented a lakehouse+documents layer that extends convention agentic memory tiers (working, semantic, episodic, procedural) with what I call "institutional" memory, i.e., what an invoice reconciliation agent, say, needs to know from C360 data sources, etc.
- mmeyerlein 11d agoYeah, smart, I really like BEAM/OTP. In one of the early versions, I actually built my project using Elixir because I really like its mature message passing. But then I ran into limitations. What I wanted was hard isolation per actor. I also wanted a single binary on Linux. Landlock and seccomp are really cool. But I still miss BEAM's supervision trees and hot code loading. That was a bit clunky in Rust.