Rendered at 01:34:01 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
hyperman1 3 days ago [-]
I feel the basic premise here is wrong. People do not choose C++ because of trust(ing they cannot back themselves in a corner).
Main reasons are more: Our people know it, our vendors support it, our libraries use it, our workflow is built for it, etc. It is understanding that the cultural work has been done. The cost of switching is huge.
That's a good reason, but it is also the reason why people start new Cobol applications in 2026.
The other reasons for C++ were very good control of the lowest level, and very good performance, combined with decent ergonomics. You could have some of these (eg fortran's performance being better than C's), but rust brought a new player that gave this too, and bringing much better stability as a bonus.
If you have a huge C++ code base, looking into things like this might be worth it. But if you start without knowledge of either C++ or Rust, choosing C++ would probably be a bad idea .
leontheyellow 2 days ago [-]
You have solid points.
RustCC only humbly borrows Rust abstractions into a CC profiler. If that helps the existing or new CC code, which is already good. Personally, I use Rust too. That is the inspiration of RustCC.
BTW, RustCC may have identified an NCCL potentially UB bug. Waiting for NCCL to review.
Main reasons are more: Our people know it, our vendors support it, our libraries use it, our workflow is built for it, etc. It is understanding that the cultural work has been done. The cost of switching is huge.
That's a good reason, but it is also the reason why people start new Cobol applications in 2026.
The other reasons for C++ were very good control of the lowest level, and very good performance, combined with decent ergonomics. You could have some of these (eg fortran's performance being better than C's), but rust brought a new player that gave this too, and bringing much better stability as a bonus.
If you have a huge C++ code base, looking into things like this might be worth it. But if you start without knowledge of either C++ or Rust, choosing C++ would probably be a bad idea .
RustCC only humbly borrows Rust abstractions into a CC profiler. If that helps the existing or new CC code, which is already good. Personally, I use Rust too. That is the inspiration of RustCC.
BTW, RustCC may have identified an NCCL potentially UB bug. Waiting for NCCL to review.
https://github.com/NVIDIA/nccl/issues/2062