Swift is getting really mature. Stable ABI. Using clang to access and represent C++ types natively. No ffi bindings required. Foundation library available on all desktop platforms.
I hope Rust will start putting some serious effort behind C++ migration/interop. Or I can see a future where the C++ industry migrates largely to Swift, with perhaps Rust libraries for specific tasks like codecs. Which is fine but I worry about some companies, that would be willing to use Rust, never catching up to that.
C++ code will never migrate directly into Safe Rust. Swift found a middle ground for it that Rust will need too. Unsafe Rust needs to become a language people can do their daily work in that is better than C++. That’s what migration can look like.
I was skeptical of Carbon’s plan to build out an unsafe language that is good to work in, since I felt like the safe language is where people should be. I still worry about coming in and building the safe language later, but I can see the value of making an ergonomic unsafe language (nullability for pointers for example), because they are taking seriously the idea of migrating whole C++ codebases to this language. AND understanding that people will be working in that (unsafe) language full time.
1/2
#Cpp #Rust #Swift #CarbonLang
dana :blobhaj_witch: /
npub18r…6ummd
2023-11-22 15:38:38
Author Public Key
npub18r2scut9sdq9x05phzxkxe7f9uruppns23ekp8flq33r94yk3ljsh6ummdPublished at
2023-11-22 15:38:38Event JSON
{
"id": "fc62e9cdddea4a5d2a5767f73e7ac09188ba6019a21d873b4b3061a0186cc949",
"pubkey": "38d50c71658340533e81b88d6367c92f07c086705473609d3f046232d4968fe5",
"created_at": 1700667518,
"kind": 1,
"tags": [
[
"t",
"cpp"
],
[
"t",
"rust"
],
[
"t",
"swift"
],
[
"t",
"carbonlang"
],
[
"proxy",
"https://sunny.garden/users/blinkygal/statuses/111454946462645613",
"activitypub"
]
],
"content": "Swift is getting really mature. Stable ABI. Using clang to access and represent C++ types natively. No ffi bindings required. Foundation library available on all desktop platforms. \n\nI hope Rust will start putting some serious effort behind C++ migration/interop. Or I can see a future where the C++ industry migrates largely to Swift, with perhaps Rust libraries for specific tasks like codecs. Which is fine but I worry about some companies, that would be willing to use Rust, never catching up to that. \n\nC++ code will never migrate directly into Safe Rust. Swift found a middle ground for it that Rust will need too. Unsafe Rust needs to become a language people can do their daily work in that is better than C++. That’s what migration can look like.\n\nI was skeptical of Carbon’s plan to build out an unsafe language that is good to work in, since I felt like the safe language is where people should be. I still worry about coming in and building the safe language later, but I can see the value of making an ergonomic unsafe language (nullability for pointers for example), because they are taking seriously the idea of migrating whole C++ codebases to this language. AND understanding that people will be working in that (unsafe) language full time.\n\n1/2\n\n#Cpp #Rust #Swift #CarbonLang",
"sig": "d02183f5ca6c5a6b25bac3f16488544865d627eb9a9a2442473df6faa72a900f0e1c75f9f7700d850a606b9b54647cd054f713af0668b759aae2013fbc8b4c4d"
}