<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dependencies on Jake Worth</title>
    <link>https://jakeworth.com/tags/dependencies/</link>
    <description>Recent content in Dependencies on Jake Worth</description>
    <image>
      <title>Jake Worth</title>
      <url>https://jakeworth.com/twittercard.png</url>
      <link>https://jakeworth.com/twittercard.png</link>
    </image>
    <generator>Hugo -- 0.159.1</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Apr 2026 15:54:06 -0400</lastBuildDate>
    <atom:link href="https://jakeworth.com/tags/dependencies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tradeoffs of Permanently Forking a Library</title>
      <link>https://jakeworth.com/posts/permanently-forking-a-library-tradeoffs/</link>
      <pubDate>Fri, 03 Apr 2026 15:54:06 -0400</pubDate>
      <guid>https://jakeworth.com/posts/permanently-forking-a-library-tradeoffs/</guid>
      <description>&lt;p&gt;Permanently forking a library is something I&amp;rsquo;ve observed on several teams. The ability to fork an open-source project is a technological and social marvel. But, there are tradeoffs that aren&amp;rsquo;t always obvious.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
