kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
<JacobWeisz[m]>
That reminds me of my favorite recent targeted-code story, kentonv: https://forums.flightsimlabs.com/index.php?/announcement/11-a320-x-drm-what-happened/
<JacobWeisz[m]>
So yeah, definitely would look extremely suspicious, lol.
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 258 seconds]
<kentonv>
JacobWeisz[m], sure, it potentially replaces CapRedirector. FWIW, though, that the motivation for me working on that was for use in Workers, not Sandstorm.
<JacobWeisz[m]>
I figured, the description just made it sound like code deletion was also possible.
<kentonv>
(rebooting)
kentonv has quit [Quit: Leaving]
kentonv has joined #sandstorm
<isd>
We'd have to port the sandstorm code over to use it, can't just hit "delete," but yeah there's a comment in the sandstorm implementation about how someday we should push this into capnp.
<JacobWeisz[m]>
Should I open an issue to track it?
<isd>
Sure, why not.
<JacobWeisz[m]>
(I imagine there's inherent value in replacing only-used-by-Sandstorm code with used-by-Cloudflare-Workers code because the latter is likely to see greater scrutiny/improvement.)
<isd>
In this case the sandstorm version also in theory has some performance disadvantages, iirc.
<kentonv>
I mean, it's a fairly small utility class, so I'd say it's not a huge deal, but yes it would be nice to clean up eventually
<kentonv>
and arguably right now, the Sandstorm one is far more proven. :)
<isd>
Yeah, I don't see this as high-priority.
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 240 seconds]