5 ms·
> Like, why don't we just let projects be "done"? Things don't need to be maintained and updated for eternity. This is generally why I opt for "single-file" li
by bArray 5y ago
> Like, why don't we just let projects be "done"? Things don't need to be maintained and updated for eternity.
This is generally why I opt for "single-file" libraries that do one simple task well. The smaller the library, the more likely it is "done". For example, do I want some insanely complex image library that handles every file format under the sun, or do I just want some basic one that allows me to output a simple JPEG?
I often find myself referring to "single_file_libs" repository: https://github.com/nothings/single_file_libs https://github.com/nothings/single_file_libs
Looking at the open issues, it doesn't appear to be actively maintained but it's still an incredibly good resource for "completed" projects.
- bjterry 5y ago> Looking at the open issues, it doesn't appear to be actively maintained I'm not sure if this is intentionally ironic or not, but it does seem like if your small libraries aren't getting updated regularly because they are done, you at least want the meta library (in this case the single file libs repository) to be updated regularly with new small libraries.
- bArray 5y ago> [..] you at least want the meta library (in this case the single file libs repository) to be updated regularly with new small libraries. It's the meta-library collection repository I was talking about, not the single-file libraries.
- bmicraft 5y agoFunny you chose to say jpeg, because jpegxl is just on it's way to getting big. If you're dealing with a lot of images the savings are probably big enough to warrant an update. There really is nothing that can be considered completely stable.