3 ms·
This is a great list, primarily for learning and experimenting. However I would not use these for production purpose. Typically production apps require Security
by israrkhan 10y ago
This is a great list, primarily for learning and experimenting. However I would not use these for production purpose. Typically production apps require Security, Performance, handling of edge cases, Memory leaks, and reliability in addition to functionality. It is easier to implement functionality in a single file library, however the scope increases significantly when you start adding things like os/hw/api abstraction layers, and aspects other than functionality.
- ovao 10y agoYou've not explained how a header-only approach precludes "security, performance, handling of edge cases, memory leaks [presumably you mean the absence of] and reliability".
- cgvgffyv 10y agoLeave him be, he must've just learned all those words, and in the great tradition of average human discourse, put them together to form a grammatically coherent yet nonsensical utterance that nonetheless achieves its main objective, namely making him feel good about himself. (See? I can do it too!)
- djsumdog 10y agoSo when you talk about security, you're usually talking about package management. The idea being, if you use official packages that are maintained, security advisories can be patched and you can get those with updates. At the same time, many of the major C++ applications we use don't use package management/external dependencies. Sometimes it's for security, but mostly it's for stability and reproducibility in bug management. Firefox has its own embedded PNG, JPEG et. al. libraries. Professor Silvio from Australia has done a lot of work on identifying outdated libraries with security vulnerability embedded in C/C++ projects.