jpeeler
Joined 10 years ago
Joined 10 years ago
A decade ago Moxie Marlinspike argued[1] that to develop Signal more quickly, he and his team could not be distracted by federation. At the time I wasn't sure what to think, but it does seem that the effort level of using the integrated approach of client/server/protocol may just logistically be easier.
https://youtu.be/34r8Ypxzkk4 (28:42-28:54)
https://github.com/systemd/systemd/releases/tag/v254
Soft rebooting was even more exciting for me, but I wasn't able to get it to work on my bluebuild based system (customized universal blue). I haven't tried it in a while though.
It bothers me that the Claude Code leak (from what I read, didn't look) a few months ago showed a lot of careful consideration for context handling. I assume this means that each harness performance/correctness would differ drastically just from this alone.
I've been considering switching my approach to using a microVM through microsandbox[3]. The pro of this approach is you can essentially skip the policies and rely on the security of the VM boundary. The negative is that now you've lost all your installed tools, so you need to either provision at runtime or build something (like an image) beforehand to match your dev environment.
I still don't know which is less maintenance. And while I think herde is pretty well thought out, I do think about something that works outside the terminal may be nicer.
[1] https://github.com/ogulcancelik/herdr