4 ms·
> like BoringSSL, but Swift-native solutions are becoming more common. I've seen this one, "Move away from BoringSSL", actively in development (PR opened two w
by BrianHenryIE 3y ago
> like BoringSSL, but Swift-native solutions are becoming more common.
I've seen this one, "Move away from BoringSSL", actively in development (PR opened two weeks ago):
https://github.com/vapor/jwt-kit/pull/99 https://github.com/vapor/jwt-kit/pull/99
- favorited 3y agoNice! It looks like they were vendoring their own copy of it, and don't have to anymore. Now they're using `swift-certificates` and `swift-asn1`, which both got open-sourced in May. That's why I try to push back when people say Apple "doesn't care" about server-side Swift – they're regularly releasing these packages that they wouldn't bother open-sourcing and maintaining if they "didn't care." Things like NIO-based implementations of IMAP and SSH, an OpenAPI generator & runtime, HTTP type abstractions, a Cassandra client, etc. Most of those are from the last year, in addition to those certificate packages. They're paying teams of full-time employee salaries to work on this stuff, including open-sourcing it.