<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Game-Engine on Birdor Blog</title>
		<link>https://blog.birdor.com/tags/game-engine/</link>
		<description>Recent content in Game-Engine on Birdor Blog</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sat, 06 Jun 2026 10:20:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.birdor.com/tags/game-engine/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>A Practical Tech Stack for Indie Game Developers</title>
				<link>https://blog.birdor.com/indie-game-tech-stack/</link>
				<pubDate>Sat, 06 Jun 2026 10:20:00 +0800</pubDate>
				<guid>https://blog.birdor.com/indie-game-tech-stack/</guid>
				<description>&lt;p&gt;An indie game tech stack should help the developer finish the game.&lt;/p&gt;&#xA;&lt;p&gt;That sounds obvious, but many developers choose tools for the wrong reasons:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the engine looks powerful&lt;/li&gt;&#xA;&lt;li&gt;the language feels elegant&lt;/li&gt;&#xA;&lt;li&gt;the renderer is impressive&lt;/li&gt;&#xA;&lt;li&gt;the tool is popular in technical discussions&lt;/li&gt;&#xA;&lt;li&gt;the developer wants to learn something new&lt;/li&gt;&#xA;&lt;li&gt;the stack feels more serious than the project requires&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Learning is valuable. Technical taste matters. But a commercial or serious indie game needs a stack that supports production, not just exploration.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
