News for hackers. Stuff that matters.
Re:Never use a dependency that you could replace with an aft... by ori_b on Tuesday August 11, 2020 @03:58PM (#24125246)
And when you run into a bug or design problem in a dependency of a dependency of a dependency?

It often takes less time to write some code than to understand someone else's code.

Most programmers I've worked with get lost easily when jumping through layers of other people's code. I certainly do.

Solid, well tested dependencies that solve hard problems are worthwhile. But dependencies have a cost in debuggability and maintenance, so it's worth using them with care. And often, they aren't worth the time, when compared to writing a dozen lines of code.

Re:Never use a dependency that you could replace with an aft... by eberkund on Tuesday August 11, 2020 @04:36PM (#24125669)
I get easily lost jumping through layers of code written by corporate developers in an afternoon. I generally don't have problems jumping through layers of popular, well documented and single-purpose third-party libraries.
Re:Never use a dependency that you could replace with an aft... by quest88 on Wednesday August 12, 2020 @12:24PM (#24133644)
Cross that bridge when you get there.