Apparently the telecom industry uses DTLS, not QUIC, and eventually wants post-quantum cryptography for regulatory reasons, so needs DTLS 1.3.

There were massive improvements to performance in some of the areas criticized by PyCA and haproxy. X.509 handling will also be faster in the average case, with more improvements planned for 4.2.

See https://openssl2026.sched.com/event/2VSQR/performance-the-li... and its slides https://2026.openssl-conference.org/slides/2026-d3-1400-perf.... Recording should also be available soon-ish.

But even with those massive improvements, it's still slower than 1.1.1.

Doesn't seem to work with a test export I made for MacPorts: http://first-commit.com/neverpanic/macports-ports says https://github.com/neverpanic/macports-ports/commit/46e4271b... is the first commit, but it really is https://github.com/neverpanic/macports-ports/commit/876ca392....

It can, in theory. In practice, there are some ports that actually need a full Xcode installation to build, and those would just fail without Xcode.

In an ideal world, there would be a dependency declared on Xcode for all those ports so MacPorts would work with command line tools only and fail gracefully whenever Xcode is required. However, that is currently not the case because nobody implemented an easy and automated way to tell whether a port will build fine without Xcode.