<story><title>Hooking Go from Rust</title><url>https://metalbear.co/blog/hooking-go-from-rust-hitchhikers-guide-to-the-go-laxy/</url></story><parent_chain></parent_chain><comment><author>metadat</author><text>This is badass, thanks for sharing @carride.  In celebration that it&amp;#x27;s Friday, I&amp;#x27;m going to test it out right now.&lt;p&gt;In case the author happens to see this and can respond, how did you figure all of this out?  Would really enjoy a deep dive covering your process.  This is brilliant.&lt;p&gt;I also wonder if it could be extended to Nim, Zig, or any other less-straightforward hookable languages [than C&amp;#x2F;C++].&lt;p&gt;Edit: Apologies, maybe this is not that interesting of a wonderment. I did a little research and both Nim and Zig interface with libc.&lt;p&gt;I&amp;#x27;m not yet clear on whether node.js or Deno use libc, if any fellow HNers know please leave a reply!  If they don&amp;#x27;t use libc, they could be interesting targets.</text></comment>
<story><title>Hooking Go from Rust</title><url>https://metalbear.co/blog/hooking-go-from-rust-hitchhikers-guide-to-the-go-laxy/</url></story><parent_chain></parent_chain><comment><author>zasdffaa</author><text>&amp;gt; Golang doesn’t use libc on Linux, and instead calls syscalls directly&lt;p&gt;Could someone explain this. I&amp;#x27;m not familiar with low level linux stuff. Why would you choose not to use libc, what are the implications?</text></comment>