<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Haxe on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/haxe/</link>
    <description>Recent content in Haxe on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/haxe/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Haxe vs HashLink vs OpenFL in 2026: Which Cross-Platform Stack Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-24-haxe-vs-hashlink-vs-openfl-cross-platform-stack-guide/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-24-haxe-vs-hashlink-vs-openfl-cross-platform-stack-guide/</guid>
      <description>&lt;p&gt;One codebase, and you can ship the exact same source to a native C++ desktop binary, a JavaScript bundle, an Android app, a JVM jar, a PHP file and a WebAssembly module. Haxe has done that since 2005 — and as of &lt;strong&gt;2026-09-23&lt;/strong&gt; the compiler repo was still receiving commits at &lt;strong&gt;6,939 stars&lt;/strong&gt;. The hard part isn&amp;rsquo;t the technology. The hard part is that nobody can tell you what the difference is between Haxe, HashLink, Lime, OpenFL, HaxeFlixel and HaxeUI — or which of those six names you actually need to install.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
