3 ms·

I feel like the whole issue with c++ is that in order to create a language able to do everything you more or less have to include a feature set that is 'unharmo

by Verdex 2y ago

I feel like the whole issue with c++ is that in order to create a language able to do everything you more or less have to include a feature set that is 'unharmonious' to say the least. To me it kind of feels like swift's place here is going to replace the subset of c++ that apple is mostly interested in. But not necessarily the c++ that they aren't and then likely not the c++ that rust et al are able to replace (although I guess we'll see what they have in mind as time goes by). I suspect they'll be disappointed if they try to replace c++ in totality. As the end result will likely not be particularly habitable.

MBCook 2y ago
> 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.