News for hackers. Stuff that matters.
Re:Std::visit is everything wrong with modern C++ (2017) by DerDangDerDang on Saturday December 05, 2020 @12:18PM (#25316237)
All true. Ironically the main thing keeping C++ relevant is the lack of a standard cross platform ABI. The moment interop with the C++ ecosystem becomes easier, the newer languages look so much more attractive.
Re:Std::visit is everything wrong with modern C++ (2017) by rualca on Sunday December 06, 2020 @03:30AM (#25322041)
> Ironically the main thing keeping C++ relevant is the lack of a standard cross platform ABI.

I find that statement very odd, because in my experience the bane of C++, and perhaps the primary reason to look for alternatives, is C++'s lack of a standard ABI.

The lack of a stable ABI is C++'s main source of bit rot, and the main technical point that justifies migrating projects, even legacy ones, into other programming languages. If not for the ABI issue, most of the technical points used in favour of jumping away from C++ into some bandwagon of the moment would be moot.

Re:Std::visit is everything wrong with modern C++ (2017) by Gibbon1 on Sunday December 06, 2020 @03:57AM (#25322159)
If C++ had a stable defined API then you could just import a C++ library blob into python, or rust, or whatever and it would just work. That you can't is what keeps people developing projects in C++ instead of more productive and sane languages.
Re:Std::visit is everything wrong with modern C++ (2017) by DerDangDerDang on Sunday December 06, 2020 @08:39AM (#25323401)
Yeah, 'ironically' because although your points are quite correct, so are Gibbon1's.

'paradoxically' would have been a better word choice on my part

Re:Std::visit is everything wrong with modern C++ (2017) by spaetzleesser on Saturday December 05, 2020 @10:32PM (#25320780)
Very true. It also makes working with C++ harder. It’s so easy to use different libraries with C#, Java or Python vs the struggle it is to integrate a C++ library.