<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Generics on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/generics/</link>
    <description>Recent content in Generics on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/generics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Generics Libraries in 2026: samber/lo vs go-funk vs pie — Which One Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-27-go-generics-libraries-samber-lo-go-funk-pie-comparison/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-27-go-generics-libraries-samber-lo-go-funk-pie-comparison/</guid>
      <description>&lt;p&gt;Go developers spend an absurd amount of time writing the same five loops: filter a slice, map over it, check if it contains a value, find the first match, sum the results. Before Go 1.18 there was no type-safe way to share that code, so the ecosystem split into two camps: reflection-based helpers that work with any type but panic at runtime, and hand-written per-type functions that are safe but tedious. Generics changed the calculus in 2022 — and by 2026 the landscape has consolidated around three libraries with very different philosophies: &lt;strong&gt;samber/lo&lt;/strong&gt; (21,412 stars, a Lodash-style toolbox built on generics), &lt;strong&gt;go-funk&lt;/strong&gt; (the reflection-era veteran, now effectively dormant), and &lt;strong&gt;pie&lt;/strong&gt; (a focused, type-safe slice-and-map library). Here is how they compare with live repository data and real code, and which one you should reach for in your next module.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
