<story><title>How to write better game libraries</title><url>https://handmade.network/wiki/7138-how_to_write_better_game_libraries</url></story><parent_chain></parent_chain><comment><author>NohatCoder</author><text>It always baffles me when a library comes with its own arcane build code. Instructions like &amp;quot;Requires Python&amp;quot; invariably turn out to actually mean &amp;quot;Requires hours of debugging&amp;quot;.</text></comment>
<story><title>How to write better game libraries</title><url>https://handmade.network/wiki/7138-how_to_write_better_game_libraries</url></story><parent_chain></parent_chain><comment><author>saagarjha</author><text>I don&amp;#x27;t see it mentioned, but it&amp;#x27;s important to note that you don&amp;#x27;t have to write your library in the same language that you expose to your users. You can write everything in C++&amp;#x2F;Rust&amp;#x2F;Python and expose something compatible with the C ABI and people will be able to use it (provided they have your toolchain…)</text></comment>