5 ms·

I've seen this happen so many times. "We can't use X because it doesn't come with library Y!" And then they point to their favorite alternative to X, and note t

I've seen this happen so many times. "We can't use X because it doesn't come with library Y!" And then they point to their favorite alternative to X, and note that it does have library Y, and ignore just how utterly terrible that library is. Sometimes it's better to rewrite a library yourself than use an existing one that gets in the way as often as it helps.

this_user 12y ago
> Sometimes it's better to rewrite a library yourself than use an existing one that gets in the way as often as it helps. Sometimes, but not most of the time. Most of the time your own library will be just as terrible as the one you were trying to replace. This is especially true when it is done by someone who is not good at designing APIs. In then end you then get something that is barely documented, slow and full of bugs. I would know, I have removed more than my fair share of crappy inhouse libraries from projects.