3 ms·
Something I never see mentioned, and something that's honestly the biggest barrier to me adopting an appropriately licensed third party library or framework, is
by taneq 10y ago
Something I never see mentioned, and something that's honestly the biggest barrier to me adopting an appropriately licensed third party library or framework, is code style. If you use several libraries with significantly different coding style, your own code becomes a horrible mishmash of random capitalisation, calling conventions, allocation/deallocation/ownership conventions, etc. and your ability to easily interpret your own code goes out the window.
What I usually end up doing is wrapping each third party library with a thin wrapper which uses my own conventions, to isolate the differences, but still, this is a pain. When you add this pain to the pain of finding a library that does what I want, and the pain of figuring out how to use it despite often poor documentation, and the pain of having to debug weird edge cases that the developer never encountered, you get a pretty sizable disincentive compared with just implementing your own.