The list of &quot;recommended reading&quot; from one of the issues looks great:<a href="https:&#x2F;&#x2F;github.com&#x2F;a-e-k&#x2F;canvas_ity&#x2F;issues&#x2F;11#issuecomment-2764448070" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;a-e-k&#x2F;canvas_ity&#x2F;issues&#x2F;11#issuecomment-2...</a>

The project is great. The HN comments are embarrassing. Isn’t it ironic to imply laziness by chiming in with “vibe coded” which in itself is such a lazy reaction.

It is common for header-only libraries: you need to include this header in one c++ using the macro for linking (don&#x27;t use that macro in other c++ files to avoid duplicate symbols). In C++, you can declare a function as many times as you want, but you can only define it (write the actual body) once in the entire project.

that&#x27;s a common pattern in C++ land because there is no standard way to use libraries in C++<a href="https:&#x2F;&#x2F;github.com&#x2F;p-ranav&#x2F;awesome-hpp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;p-ranav&#x2F;awesome-hpp</a>

Thank you for sharing. The only thing I don&#x27;t understand why this is a header only implementation with a macro that goes in a C++ file.<pre><code> #define CANVAS_ITY_IMPLEMENTATION</code></pre>

It would be interesting to compile to WASM to compare side by side for performance and accuracy.

Most likely not seeing as the commit containing the bulk of the implementation dropped in 2022.

Yes, it&#x27;s a canvas library, there&#x27;s a lot of risks of including AI generated code that hasn&#x27;t been checked in a rasterizing library.

Canvas_ity: A tiny, single-header <canvas>-like 2D rasterizer for C++