swift-metrics VS swift-statsd-client

Also, Apple seems to be putting a ton of work into the Swift-on-server ecosystem. They've released packages for things like tracing, metrics, service discovery, logging, etc. And most of those are basically shared interfaces, and then Apple (or the community) will write backend implementations, like one for statsd which implements the stuff from swift-metrics.

Apple is investing a lot in it, but Swift is much younger than Rust (especially as an open source project). There is a working group that meets every few weeks to shepherd the various projects. Most of the recent activity has been (AFAICT) about orchestration. Well, that and transitioning projects to use async/await and structured concurrency. Here's some recent activity in the Swift on server space:

- the proposal for distributed actors is currently in-review (https://github.com/apple/swift-evolution/blob/main/proposals...)

- a metrics API for backends like Graphite, Prometheus, etc. (https://github.com/apple/swift-metrics)

- HTTP/2 support for SwiftNIO (https://github.com/apple/swift-nio-http2)

- a new service discovery API (https://github.com/apple/swift-service-discovery)

- a new distributed tracing API (https://github.com/apple/swift-distributed-tracing)

- a Linux implementation of Apple's CryptoKit API on top of BoringSSL (https://github.com/apple/swift-crypto)

I'm not pretending that it's taking the server-side world by storm, but there is a fair amount of ongoing activity Personally, I'm using it for a couple personal projects and it's been solid, but I'm already a macOS developer, so it wasn't a big stretch for me to reach for it.

Also, Apple seems to be putting a ton of work into the Swift-on-server ecosystem. They've released packages for things like tracing, metrics, service discovery, logging, etc. And most of those are basically shared interfaces, and then Apple (or the community) will write backend implementations, like one for statsd which implements the stuff from swift-metrics.