<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Interoperability on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/interoperability/</link>
    <description>Recent content in Interoperability on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 08 Nov 2025 14:57:44 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/interoperability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using C libraries in Zig</title>
      <link>https://www.bradcypert.com/using-c-libraries-in-zig/</link>
      <pubDate>Sat, 08 Nov 2025 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/using-c-libraries-in-zig/</guid>
      <description>&lt;p&gt;Hey, everyone! Welcome to this tutorial where we&#39;ll explore one of Zig&#39;s most powerful features. Today, we&#39;re going to see how easy it is to use existing C libraries directly from Zig code.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-c-interoperability-matters&#34;&gt;Why C Interoperability Matters&lt;/h2&gt;&#xA;&lt;p&gt;One of the things that got me really excited about a different language, Clojure, when I was learning it was that although the Clojure ecosystem felt small, I had interoperability with anything that ran on the JVM. So you could interop with Java, Scala, eventually Kotlin after Kotlin really kind of caught on. It was great.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
