News for hackers. Stuff that matters.
Re:The Year of C++ Successor Languages by mgaunard on Monday January 02, 2023 @08:51AM (#34217803)
I'm sorry to hear that you haven't been successful in using C++ features to their full potential in environments tightled coupled with C libraries. Integration with C or C-like code usually requires some effort if you want to be able to use exceptions that could propagate through C.

I do not offer consulting but can refer you to people who do.

Re:The Year of C++ Successor Languages by Yoric on Monday January 02, 2023 @09:09AM (#34217968)
Thanks. Do you think they'll have time to rewrite Firefox? :) (or Chrome, which encounters the same issues)
Re:The Year of C++ Successor Languages by moloch-hai on Monday January 02, 2023 @09:43AM (#34218341)
Maybe switch to the SerenityOS browser.
Re:The Year of C++ Successor Languages by Yoric on Monday January 02, 2023 @12:58PM (#34221176)
I'll be sure to suggest that to Mozilla and Google :)
Re:The Year of C++ Successor Languages by mgaunard on Monday January 02, 2023 @06:04PM (#34224971)
Well, from what you were saying, it's mostly a problem of making your asynchronous framework work well with exceptions. It is true that you need to do special things for asynchronous programming to work well in C++, be it for exceptions or even the scope-bound lifetime management of C++ in general, which all have a huge impact on the design of your system.

In particular most multi-threaded C++ code is incorrect, not because it is impossible to do it correctly, but because the standard tooling is too low-level, each third-party framework targets a different niche, and people who roll their own tend to hack it together.

I understand Seastar is supposed to do it somewhat correctly, so you could suggest to Mozilla that they switch to that.