IRC channel logs

2025-09-23.log

back to list of logs

<jfred>I saw the cloudflare library, looks neat. I wish it were ocapn-compatible of course but if this helps the ideas get out there some more I think that's good. (And their intro docs in the README are very good, it's got a nice easy on-ramp)
<lxsameer>hey folks, Has Hoot have its own channel?
<dthompson>lxsameer: no, this channel is the place to talk about all spritely things. I also hang out in #guile so you can talk about it there, too
<lxsameer>cool, so does hoot supports WASI, or is it wasm only?
<dthompson>no wasi support
<lxsameer>ah, thanks
<dthompson>last I checked there was no way to make that work with the current state of wasi
<lxsameer>how come?
<dthompson>it's just not really built for wasm gc use cases, from what I can see
<lxsameer>ah gotcha
<dthompson>passing by reference is a complicated thing that resembles borrow checking in rust https://component-model.bytecodealliance.org/design/wit.html#resources
<dthompson> jfred: yeah hopefully it's good for spreading ocap ideas, generally. I asked kentonv why not ocapn over on lobste.rs and he listed some reasons.
<dthompson>one thing that was clear is that the ocapn website just hasn't been updated in nearly a year and it paints a misleading picture of the state of things
<dthompson>the relevant lobste.rs post: https://lobste.rs/c/frjjwl
<jfred>I hope the outdated website wasn't too big a factor in the decision to write a totally new one ^^;
<dthompson>I think kentonv would have done his own thing regardless
<dthompson>cloudflare can move faster without working in a standards group, also
<ridley>and they have just a tad more resources than the rest of us
<dthompson>ridley: just a bit
<dthompson>a few bucks