Never use a dependency that you could replace with an afternoon of programming

Re:Never use a dependency that you could replace with an aft... by vlovich123 on Tuesday August 11, 2020 @03:55PM (#24125210)

Depends how your dependency management system works. Some times it can take an afternoon or more just to integrate it into your build for c/c++

[ Parent | on HN ]

Re:Never use a dependency that you could replace with an aft... by avmich on Tuesday August 11, 2020 @04:00PM (#24125274)

Somehow here we assume a good programmer routinely makes errors in time estimation by an order of magnitude, yet conveniently forget cases when, say, a non-trivial GPL library is embedded as a dependency into a project, and customer is asking for code, and legal team runs with hairs on fire because company didn't plan to release the code...

[ Parent | on HN ]

Re:Never use a dependency that you could replace with an aft... by greyhair on Wednesday August 12, 2020 @09:33AM (#24131902)

But that is a completely different topic. Licensing is an issue, yes, but that is part of the upfront decision process.

In this day an age, this many years into open source licensing, if your team is not on top of that from day one, they have failed as a team.

I worked at Bell Labs from the mid 1980s to 2000, and by early 1990s (1992? 1993?) they already had a full internal team dedicated to open source licensing issues, including training and consulting. That was 27 or 28 years ago. Before some of the developers on this thread were even born.

[ Parent | on HN ]