8 ms·
There is one thing about Swift vs C++. Like C, Swift now has a stable ABI. C++ will never have a stable ABI. Better now to start abandoning C++ for better langu
by Gibbon1 6y ago
There is one thing about Swift vs C++. Like C, Swift now has a stable ABI. C++ will never have a stable ABI. Better now to start abandoning C++ for better languages.
- pjmlp 6y agoC never had a stable ABI to start with. That is a misconception from developers that don't understand C ABI == OS ABI, on OSes that happen to be written in C. There is no C ABI on IBM and Unisys mainframes, Android, ChromeOS, WebAssembly and plenty of other OSes written in other languages. OS/2 SOM, Windows COM and UWP are ways to achieve a compromise regarding how to expose a C++ ABI in a language neutral way. And stuff like gRPC also allows for something similar with inProcess calls. Many of those better languages depend on LLVM, so no C++ is not going nowhere for the foreseeable future.
- Gibbon1 6y agoProblem we had was language designers spent 15 years targeting the JVM for new languages. But now finally there are good native languages like Rust, Swift, Golang, etc. Next thing is to write full compilers in those languages and ditch C++ and LLVM.
- pjmlp 6y agoGood luck getting Apple, Google, Microsoft, IBM, ARM, NVidia, Khronos, or industry standards like AUTOSAR to ditch C++. In fact they seem more focused on bringing Rust like capabilities to C++ static analysers, than anything else. JVM has always been native by the way, for those that bothered to get hold of commercial AOT compilers, like PTC, J/Rockit, Excelsior among many others.
- gpderetta 6y agoon systems that use the Itanium ABI, the C++ ABI is as standard as the C one.