<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Firefly Zero blog</title>
    <link>https://blog.fireflyzero.com/</link>
    <description>Recent content on Firefly Zero blog</description>
    <generator>Hugo -- 0.155.3</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.fireflyzero.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why we&#39;re staying on Discord</title>
      <link>https://blog.fireflyzero.com/pages/discord/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.fireflyzero.com/pages/discord/</guid>
      <description>&lt;h2 id=&#34;discord&#34;&gt;Discord&lt;/h2&gt;
&lt;p&gt;Shortly after I started working on &lt;a href=&#34;https://fireflyzero.com/&#34;&gt;Firefly Zero&lt;/a&gt;, I registered a bunch of social accounts: Mastodon, Bsky, and Xitter. While I personally only use Mastodon, I want to provide everyone a convenient way to get project updates in their own favorite place. You can contribute to our projects from any OS and IDE, so why should I limit where you get you updates?&lt;/p&gt;
&lt;p&gt;Discord followed shortly after, with the same motivation and purpose. I created two channels: &lt;code&gt;#general&lt;/code&gt; where Discord would post a message for every new person joining (and others would send a &amp;ldquo;waving hand emoji&amp;rdquo; to acknowledge the fact) and &lt;code&gt;#releases&lt;/code&gt; where I would post the same updates as on all other media.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Call for games</title>
      <link>https://blog.fireflyzero.com/pages/call-for-games/</link>
      <pubDate>Sat, 21 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.fireflyzero.com/pages/call-for-games/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re making a cool game console and we need you to make cool games for it.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://fireflyzero.com/&#34;&gt;Firefly Zero&lt;/a&gt; is a handheld game console, similar to &lt;a href=&#34;https://en.wikipedia.org/wiki/Game_Boy_Advance&#34;&gt;Game Boy Advance&lt;/a&gt; (GBA). However, unlike GBA, it is modern (and easy to program), has same-room multiplayer (over Bluetooth), and uses a touchpad instead of D-pad for more precise controls.&lt;/p&gt;
&lt;h2 id=&#34;developer-experience&#34;&gt;Developer experience&lt;/h2&gt;
&lt;p&gt;Firefly Zero is a game console with the best developer experience. It is the first WebAssembly-powered handheld game console in the world. All you need to know about WebAssembly is that it is supported by almost all modern programming languages. And you can use any of them for writing Firefly Zero games!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Bringing WebAssembly to microcontrollers</title>
      <link>https://blog.fireflyzero.com/pages/history2/</link>
      <pubDate>Wed, 31 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.fireflyzero.com/pages/history2/</guid>
      <description>&lt;p&gt;This is the second and the last part of the series about the history of Firefly Zero. The first part: &lt;a href=&#34;https://blog.fireflyzero.com/pages/history1/&#34;&gt;A brief history of fantasy video game consoles&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;2017-webassembly&#34;&gt;2017. WebAssembly&lt;/h2&gt;
&lt;p&gt;We already touched a bit on WebAssembly in the first part. It was released in 2017. I started to work with WebAssembly in 2019. At the time, the only thing I knew about it was that it&amp;rsquo;s a way to write frontend code in the Go programming language instead of JavaScript. And since JavaScript is somewhere at the bottom of my top of programming languages, that was enough of a reason for me to start using WebAssembly with Go.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A brief history of fantasy video game consoles</title>
      <link>https://blog.fireflyzero.com/pages/history1/</link>
      <pubDate>Fri, 19 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.fireflyzero.com/pages/history1/</guid>
      <description>&lt;p&gt;This is the first post in the two-part series about the history of Firefly Zero. This post is dedicated to the technologies that inspired Firefly Zero, from early computers to modern programming languages.&lt;/p&gt;
&lt;p&gt;Second part: &lt;a href=&#34;https://blog.fireflyzero.com/pages/history2/&#34;&gt;Bringing WebAssembly to microcontrollers&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;1977-chip-8&#34;&gt;1977. CHIP-8&lt;/h2&gt;
&lt;p&gt;In 1977, &lt;a href=&#34;https://en.wikipedia.org/wiki/Joseph_Weisbecker&#34;&gt;Joseph Weisbecker&lt;/a&gt; released &lt;a href=&#34;https://en.wikipedia.org/wiki/COSMAC_VIP&#34;&gt;COSMAC VIP&lt;/a&gt;. It was a personal computer designed for writing and playing video games. The whole idea of video games was quite new. &lt;a href=&#34;https://en.wikipedia.org/wiki/Tetris&#34;&gt;Tetris&lt;/a&gt; was created only in 1985 (8 years after COSMAC VIP). &lt;a href=&#34;https://en.wikipedia.org/wiki/Pong&#34;&gt;Pong&lt;/a&gt; was released in 1972, but it was an arcade game, and you would play it on a special big machine designed to run just this one thing. The idea of a computer that is designed for games and can be used to both write and play them was big.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
