4 ms·

Amusingly enough, the main direction Shepherd is exploring right now is integrating Spritely Goblins (the folks that are also writing Hoot), so that it would ha

Amusingly enough, the main direction Shepherd is exploring right now is integrating Spritely Goblins (the folks that are also writing Hoot), so that it would have a distributed, capability-based process manager. I wouldn't say running Shepherd with Hoot is a direct goal of this, but it may fall out naturally from it. Shepherd may actually work in Hoot right now -- I know the Spritely team were working on getting Guile's fibers library to work in WASM, and that's probably the biggest lift.

paroneayea 2y ago
It may be possible to get Shepherd to work with Hoot eventually! I'm not sure what on earth it would mean though. What daemons would you manage in the browser? But it's indeed a fun idea!
- NeutralForest 2y ago
  If you could configure a fleet of machines from a browser window, over the network; that would be pretty cool. No clue how that would work in practice here though.
  - davexunit 2y ago
    Since everything would be speaking OCapN you could use the browser interface as a convenient command center. This idea is becoming quite appealing to me actually... would be cool to have a little dashboard showing the health of my servers and be able to restart a failed service if I needed to.
jauntywundrkind 2y ago
Wow, that's a very fun reply! Nice. Fingers crossed that the Stack Switching spec gets adopted & serves Guile Hoot's needs for fibers. https://github.com/WebAssembly/stack-switching https://github.com/WebAssembly/stack-switching
- davexunit 2y ago
  Stack switching in wasm would be great (as long as they aren't nerfed which they might be!) but note that Hoot has fibers right now: https://gitlab.com/spritely/guile-hoot/-/tree/main/lib/fibers?ref_type=heads https://gitlab.com/spritely/guile-hoot/-/tree/main/lib/fiber...