In my case, I basically never use anyone else's code, unless there's a real need for it, and if I'm quite confident in its veracity.

I also take full Responsibility and Accountability for that code, when it is running in my execution thread.

The result of this policy, is that I have written almost every single dependency that I use.

It has garnered me a lot of sneers from the "in crowd."

I don't particularly care.

WFM. YMMV.

[EDIT] Also, I like this:

    my name is always spelled lowercase and is pronounced /ɪliˈɑnə ɛˈtiːn/.

    please consider making the internet a weirder place today

    note: if you send me unsolicited email based on my github profile:

    i will screenshot it and share in my discord server
    we will make fun of you
    you will not receive a response*

I'm not trying to be flippant, but where do you draw the line of "never use anyone else's code"? You're writing that software using an operating system and editor someone else wrote. You're compiling it with software someone else wrote. If you're deploying it to users, it's hosted on someone else's code and will be run by someone else's code in that runtime.

I know. That's the classic argument that I get. Basically "what about..?"

Like I said, I know what works for me. I'm not gonna argue about it. I do know that some find my stance offensive, which I don't actually understand. I'm not attacking anyone. I'm just saying how I do it, in my own work.

I write lots of packages that I integrate into my own work. Each package is a standalone project, with tests and docs. Because they are written and maintained by a single person, I know that some folks believe this makes them "worthless," but not to me.

It's the way that I work, on my own stuff. I'm not competing with anyone here, so I fail to see the problem. If I'm just some clueless old boomer, making a hash of things, then God bless my little heart, and I'll just be tilting at windmills, over here.

So you never used any library? Not even the standard library?

If I use the SL, then I should also have no problem using some lashed-up chimera that has a dependency hierarchy that spans three continents.

Like I said, I'll do things my way.

For the record, here's the Swift Foundation Library: https://github.com/apple/swift-corelibs-foundation (I mostly write in Swift).

It has plenty of open issues: https://github.com/apple/swift-corelibs-foundation/issues?q=...

Also, for the record, here's a peek at some of the "worthless" packages that I use in my own work: https://github.com/RiftValleySoftware

If every dependency chain can match these, then I'll be open to considering them.

As it is, I do use the occasional external package, but I'm picky.