New answers tagged

2

There are many, many things that need considering that might make an off-the-shelf solution problematic. Some of the most important ones are: completeness - does it do the job you need entirely, or are you going to be spending time learning its internals in order to extend it robustness - does it do its job well, without needing constant workarounds for ...


4

It mostly depends on how deep are your changes. Wrappers can bring additional behavior, but can rarely change the existing one. For instance, if a target library writes some data to a file and you want, instead, to send this data to a database, unless the library was designed to allow that, you won't be able to change the behavior just with a wrapper. If ...


0

I don't have a silver bullet. You need to consider the amount of code in the github project, as well as whether you may assume that access to github will be no problem for your users (git is available, internet connection is available, etc). If you decide to avoid including a snapshot of the third-party code, here is a reference explaining how you can ...



Top 50 recent answers are included