3 ms·
> But for large libraries, taking a source copy is absolutely crazy. The solution is, when possible, to use (and write) smaller libraries. Many libraries are f
by knowledge-clay 5y ago
> But for large libraries, taking a source copy is absolutely crazy.
The solution is, when possible, to use (and write) smaller libraries. Many libraries are far larger and more complex than they need to be.
- dpark 5y agoDepends on what it is you need. If you really have a small need, then taking a giant dependency is very possibly a bad idea. But I have seen the opposite pretty often. “I don’t need that library. I just need this one thing. Okay, this other thing, and this. And this and this and this.” And by the time they’re done they’ve reimplemented 75% of the library in a far worse way. The most egregious example I ever saw was reimplementation of xml parsing with C++ substrings. They “didn’t need” a real xml parser. In the end, they found endless bugs with their shitty parsing logic and it turns it it was responsible for something like 50% of the (very large scale) system resource use.