> I suspect they'll be disappointed if they try to replace c++ in totality. Why is that? That is their aim, I think they’ve made it clear. They’re writing all

> I suspect they'll be disappointed if they try to replace c++ in totality. Why is that? That is their aim, I think they’ve made it clear. They’re writing all-ish new code in Swift (not always practical in existing code) from what I understand. They’re already using it for the code that runs in places like the Secure Enclave or other embedded processors. Can it replace C++ 100% everywhere today? Probably not. I don’t know enough to know why. But that absolutely appears to be the goal.