Comment by ChrisMarshallNY

Interesting couple of guys. Loved the story.

I have always been skeptical of dependency (both libraries and connected runtime services), but there’s a balance.

There’s things that we just can’t do, without a dependency. We stand on the shoulders of giants.

Right now, I’m developing and refining a demonstration client/server app, for a future article on implementing PassKeys on iOS. I require two dependencies. On the server end, I use the PHP lbuchs/WebAuthn library, and on the client end, I use KeychainSwift.

The first dependency is a requirement. Implementing that functionality myself, would be prohibitive. The second dependency is one that I could do myself, but that would add a lot of complexity to an already fairly complex project.

The moral of the story is that I always have to justify every dependency that I use, and that justification involves a lot of figuring out the pros and cons. I’m always a bit discouraged, when I see folks throwing in dependencies, willy-nilly.

I remember once, attending a class on GraphQL. It hardly mentioned the standard at all. It was a class on the abstraction dependency (A JavaScript library. Maybe something like Pandas). The class was worthless to me, as I don’t work in JS. I wanted to find out about the standard.