Remix.run Logo
Canvas_ity: A tiny, single-header <canvas>-like 2D rasterizer for C++(github.com)
29 points by PaulHoule 3 hours ago | 13 comments
nicoburns 2 hours ago | parent | next [-]

The list of "recommended reading" from one of the issues looks great:

https://github.com/a-e-k/canvas_ity/issues/11#issuecomment-2...

msephton 43 minutes ago | parent | prev | next [-]

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.

ddtaylor 32 minutes ago | parent | prev | next [-]

Thank you for sharing. The only thing I don't understand why this is a header only implementation with a macro that goes in a C++ file.

    #define CANVAS_ITY_IMPLEMENTATION
socalgal2 23 minutes ago | parent [-]

that's a common pattern in C++ land because there is no standard way to use libraries in C++

https://github.com/p-ranav/awesome-hpp

Lerc 2 hours ago | parent | prev | next [-]

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

ranger_danger 2 hours ago | parent | prev [-]

vibe-coded?

nicoburns 2 hours ago | parent | next [-]

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

ranger_danger 2 hours ago | parent [-]

maybe just the README then

flowerbreeze 2 hours ago | parent [-]

The README is older than ChatGPT too. It's very unlikely that it's vibe coded or vibe written.

peter-m80 2 hours ago | parent | prev [-]

Would that be an issue?

Amlal an hour ago | parent | next [-]

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

ivanjermakov an hour ago | parent [-]

A lot of risks compared to what? I imagine bugs in kernel drivers or disk utilities be riskier.

1bpp 2 hours ago | parent | prev [-]

Yes.