Clang fits the second half, that Apple contributes a ton to it.
CUPS is another, it was ok but not great until Apple took it in and made it work with a ton of devices, and also make vendors wake up and support it. Now Windows has a much worse printing environment, and would do well to just adopt CUPS.
Nope, one of the reasons why clang is lagging behind everyone in C++20 support is that C++17 seems to be good enough for Apple purposes regarding their use of C++, and they withdraw resources from it.
Also they don't contribute everything upstream, like the stable bitcode format used in watchOS, or the SafeC used in iBoot.
Apple hired the CUPS developer, that is why, again not started by them and they had to obey the license.
Windows a worse printing environment than CUPS? What a joke.
Well if Apple didn't contribute to Clang, it would have C++ 20 because it would be developed by all those developers that aren't Apple. How can Apple be responsible for its deficiencies and not its development?
I know you were around way back then so you probably should remember it took a bit to bring clang to feature parity with gcc. There was a lot of excitement that Apple was involved in the work, and it really did get there to the point where FreeBSD, among others, could switch to clang full time.
CUPS is another, it was ok but not great until Apple took it in and made it work with a ton of devices, and also make vendors wake up and support it. Now Windows has a much worse printing environment, and would do well to just adopt CUPS.