<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Collections-Framework on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/collections-framework/</link>
    <description>Recent content in Collections-Framework on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/collections-framework/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Eclipse Collections vs fastutil vs HPPC in 2026: Which Java Collections Library Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-13-java-collections-libraries-eclipse-collections-fastutil-hppc/</link>
      <pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-13-java-collections-libraries-eclipse-collections-fastutil-hppc/</guid>
      <description>&lt;p&gt;Every Java developer hits the same wall sooner or later: &lt;code&gt;ArrayList&amp;lt;Integer&amp;gt;&lt;/code&gt; boxes every single &lt;code&gt;int&lt;/code&gt; into an &lt;code&gt;Integer&lt;/code&gt; object, bloating memory by 3–5x and turning simple loops into garbage-collection churn. In 2026, with memory prices flat and CPU cores plentiful, the three libraries that fix this — &lt;strong&gt;Eclipse Collections, fastutil, and HPPC&lt;/strong&gt; — are more relevant than ever, yet most teams still don&amp;rsquo;t use any of them. Here is the honest, benchmark-backed breakdown of which one you should adopt.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
