<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pimple on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pimple/</link>
    <description>Recent content in Pimple on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pimple/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PHP Dependency Injection Container Comparison: PHP-DI vs Pimple vs League Container vs Auryn</title>
      <link>https://www.pistack.xyz/posts/2026-07-14-php-dependency-injection-containers-phpdi-pimple-league-auryn/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-14-php-dependency-injection-containers-phpdi-pimple-league-auryn/</guid>
      <description>&lt;p&gt;Dependency injection (DI) is the cornerstone of maintainable PHP applications. Rather than having classes construct their own dependencies, a DI container manages object creation, resolves dependency graphs, and injects configured instances. This decoupling makes code more testable, more modular, and easier to refactor. In this article, we compare four popular PHP DI containers — &lt;strong&gt;PHP-DI&lt;/strong&gt;, &lt;strong&gt;Pimple&lt;/strong&gt;, &lt;strong&gt;League Container&lt;/strong&gt;, and &lt;strong&gt;Auryn&lt;/strong&gt; — analyzing their APIs, autowiring capabilities, performance, and ideal use cases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
