{"id":21708,"date":"2016-04-08T09:20:16","date_gmt":"2016-04-08T14:20:16","guid":{"rendered":"https:\/\/blog.planview.com\/how-to-pick-dependencies-from-a-developers-point-of-view\/"},"modified":"2016-04-08T09:20:16","modified_gmt":"2016-04-08T14:20:16","slug":"how-to-pick-dependencies-from-a-developers-point-of-view","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/how-to-pick-dependencies-from-a-developers-point-of-view\/","title":{"rendered":"How to pick dependencies from a developer\u2019s point of view"},"content":{"rendered":"
\n
\"How<\/div>\n<\/figure>\n

Dependencies are an essential part of each software project. Without utilizing existing libraries the scope of a project explodes because you can’t solve every problem by yourself. Today we rely heavily on open source libraries to get the work done for us. Basically there is a library for nearly every problem and every language. But how do you pick a library especially if there are multiple of them solving the same problem? What are the requirements for a library to be used in commercial software? How do you measure the quality of a library? These questions come to my mind every time I need to decide on a dependency. Over the years I have created a criteria catalog in my head that I want to share with you in this post. So, if you are the author of a library please don’t feel offended, I’m just describing how I pick dependencies.<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n