single_file_libs

Here's a master list of most libraries like this: https://github.com/r-lyeh/single_file_libs

Rather collectible, so people do: https://github.com/nothings/single_file_libs

Yep: https://github.com/nothings/single_file_libs

Packing the entire library in a header file is a somewhat recent and much welcome trend. See for example: https://github.com/nothings/stb https://github.com/nothings/single_file_libs

> 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 Looking at the open issues, it doesn't appear to be actively maintained but it's still an incredibly good resource for "completed" projects.

Glad to hear it! It's a pretty hefty single file, so it probably won't be qualifying for https://github.com/nothings/single_file_libs anytime soon... but hopefully people find it useful nonetheless.

> I collect different C libraries as a personal stash of toolkits Might you have a write-up or link for these, and if so might you be willing to share it? I have been using Sean Barrett's libraries [0], as well as his curated list of other people's single-header libraries [1], and, like you, I am always on the lookout for new things to add to the collection :) [0] https://github.com/nothings/stb [1] https://github.com/nothings/single_file_libs

This is a good point, and a difficult one to get right. Being able to very easily fetch and integrate dependencies (e.g npm) definitely lowers the barrier, for better and worse. Single-file collections ( e.g https://github.com/nothings/single_file_libs) is a nice intermediate step.

Just a suggestion... I cannot attest for the code quality of the projects on the link below, but I find it easier to start learning from smaller code bases. So when you have a chance you could take a look at this link that lists one-to-two files libraries: https://github.com/nothings/single_file_libs I think I came across the link above here on HN a couple of weeks ago. I also study some of the libs from here: https://github.com/fffaraz/awesome-cpp. Currently I'm going trough the libs for parsing CSV files. Of them, I find this one particularly interesting: https://github.com/vincentlaucsb/csv-parser. Because of well-commented files. I hope it helps.

There is a ton of useful libraries written in C [1] [2], and I feel like there's a little revival in the last few years for using C to write "bedrock libraries", because such libraries are often easier to integrate into "foreign language" projects than C++ libraries. Those libraries also often end up in C++ projects because they are often easier to integrate into C++ projects than actual C++ libraries. [1] https://github.com/floooh/bookmarks [2] https://github.com/nothings/single_file_libs (here, C/C++ usually means "written in the common subset of C and C++")