I mean faster runtime performance, I have no clue about compilation time.
Well I'm basing this on the countless benchmarks I've seen, e.g. on phoronix over the decade.
Also you have to understand that Clang -O2 is (was) "unfair" as GCC did not enable autovectorization until -O3. This has (is being?) changed.
I regularly have atrocious transient 144p like compression artefacts and lighting absurdities using Netflix both in chrome and via their native h265 app.
It is pathetic.
Tangent if they really cared about user experience and Ecology they would implement h265 and h266 support in chromium (aka a mere function call to the embedded ffmpeg).
H266 is revolutionary but it's adoption is of zero because of AV1 lobbyists a bit like so called environmentalists once launched a RPG rocket on the superphenix thorium mankind saving reactor.
I'm pretty sure you can do that with Linux.
The hypothetical BSD networking advantages seems more and more obscolete to me, missing on most modern advances such as e.g MTCP support
https://www.multipath-tcp.org/
It's a basic gradient about human resources.