<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Coding - Category - Nimbler</title><link>https://nimbler.tech/coding/</link><description>Coding - Category - Nimbler</description><language>en</language><managingEditor>contact@nimbler.tech (Nimbler)</managingEditor><webMaster>contact@nimbler.tech (Nimbler)</webMaster><lastBuildDate>Mon, 26 Oct 2026 16:37:49 +0000</lastBuildDate><atom:link href="https://nimbler.tech/coding/" rel="self" type="application/rss+xml"/><item><title>How I cut 44% of the CPU work in a Rust WebGL game without changing a pixel</title><link>https://nimbler.tech/coding/how-i-cut-44-of-the-cpu-work-in-a-rust-webgl-game-without-changing-a-pixel/</link><pubDate>Mon, 26 Oct 2026 16:37:49 +0000</pubDate><author>contact@nimbler.tech (Nimbler)</author><guid>https://nimbler.tech/coding/how-i-cut-44-of-the-cpu-work-in-a-rust-webgl-game-without-changing-a-pixel/</guid><description>&lt;p>I build a browser game with a cast of about 110 animated cartoon
characters. You can pose them and switch between view types and interactive backgrounds.
I was able to speed up the loading time from 2s to 0.47s by dropping unnecessary calculations.&lt;/p>
&lt;p>&lt;/p></description></item></channel></rss>