<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Back-End on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/back-end/</link>
    <description>Recent content in Back-End on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/back-end/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MoneyPHP vs Brick Money vs Laravel Money in 2026: Which PHP Money Library Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-10-07-php-money-libraries-moneyphp-brick-laravel-comparison/</link>
      <pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-07-php-money-libraries-moneyphp-brick-laravel-comparison/</guid>
      <description>&lt;p&gt;Every PHP developer eventually ships a rounding bug. It usually looks harmless: a cart total of &lt;code&gt;19.99&lt;/code&gt; multiplied by &lt;code&gt;3&lt;/code&gt;, stored as a float, saved into a &lt;code&gt;FLOAT&lt;/code&gt; column, and paid out a month later with a two-cent discrepancy that your accountant notices before you do. Money is not a number — it is an amount plus a currency plus a rounding policy — and PHP&amp;rsquo;s ecosystem has three serious libraries built around that fact.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
