<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graphics-Programming on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/graphics-programming/</link>
    <description>Recent content in Graphics-Programming on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/graphics-programming/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>bgfx vs Diligent Engine vs Magnum in 2026: Which C&#43;&#43; Rendering Backend Should You Actually Build On?</title>
      <link>https://www.pistack.xyz/posts/2026-09-28-bgfx-vs-diligent-engine-vs-magnum-cpp-rendering-backends/</link>
      <pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-28-bgfx-vs-diligent-engine-vs-magnum-cpp-rendering-backends/</guid>
      <description>&lt;p&gt;You have a working prototype rendering a few million triangles, and now the product team wants it on Windows, Linux, macOS, Steam Deck, iOS, and a WebGPU-capable browser build. That is five graphics APIs — Direct3D 12, Vulkan, Metal, OpenGL, and WebGPU — and writing five hand-rolled backends means five codebases to debug every time a driver vendor ships a regression. A rendering abstraction layer exists precisely to stop that. The three serious open-source choices in 2026 are &lt;strong&gt;bgfx&lt;/strong&gt;, &lt;strong&gt;Diligent Engine&lt;/strong&gt;, and &lt;strong&gt;Magnum&lt;/strong&gt;, and they are not interchangeable: they encode three different philosophies about who owns your renderer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
