Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
1–10 of 18 posts
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#2Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#3Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#4I'm not sure why single-header is an advantage over powerful libraries such as GEGL.
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#5I'm not sure why single-header is an advantage over powerful libraries such as GEGL.
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#6I'm not sure why single-header is an advantage over powerful libraries such as GEGL.
Try to understand that "advantage" can mean different things to different people. Your perspective and usecases might be totally opposite from someone else, and that doesn't mean either of you are wrong.
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#7I'm not sure why single-header is an advantage over powerful libraries such as GEGL.
edit: Seeing that it's also C99 makes me think that embedded applications might be what this was geared toward.
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#8I'm not sure why single-header is an advantage over powerful libraries such as GEGL.
No allocation is useful for embedded / resource constrained targets.
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#9[0] https://github.com/sammycage/plutofilter/blob/main/plutofilt...
Re: Show HN: PlutoFilter- A single-header, zero-allocation image filter library in C
#10I was wondering how it would do arbitrary-sized kernels without dynamic allocation (my guess was that it would use the input/output buffer as a temporary storage). The answer is that there's a _slight_ asterix to the 'zero-allocation' - the allocation is on the stack [0], but it's small-ish (2kb) and fixed size. So in an embedded context you'd just want to make sure you have headroom for this. [0] https://github.com/…