Sigh... The traditional argument is that every dependency is of the same quality and trustworthiness of the language 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.