> I personally wouldn't invest in increasing open source adoption of an Apple property like that, unless someone has a compelling new argument for that. See he

> I personally wouldn't invest in increasing open source adoption of an Apple property like that, unless someone has a compelling new argument for that. See here for his reasoning for picking Swift: https://x.com/awesomekling/status/1822236888188498031 https://x.com/awesomekling/status/1822236888188498031 > Over the last few months, I've asked a bunch of folks to pick some little part of our project and try rewriting it in the different languages we were evaluating. The feedback was very clear: everyone preferred Swift! > First off, Swift has both memory & data race safety (as of v6). It's also a modern language with solid ergonomics. > Something that matters to us a lot is OO. Web specs & browser internals tend to be highly object-oriented, and life is easier when you can model specs closely in your code. Swift has first-class OO support, in many ways even nicer than C++. > The Swift team is also investing heavily in C++ interop, which means there's a real path to incremental adoption, not just gigantic rewrites.