3 ms·
> C++ is much more safe than C The issue Mozilla faced wasn't that it wasn't safer than C. It's that it was not safe enough for their needs. A chainsaw is safe
by Ygg2 1y ago
> C++ is much more safe than C
The issue Mozilla faced wasn't that it wasn't safer than C. It's that it was not safe enough for their needs. A chainsaw is safer than a saw blade; you still don't want to trim your beard with it.
And the C++ working group, to this day, hasn't even moved one inch to accommodate those needs. As another commenter noted, they added a feature for C++26 that Rust abandoned circa 2019.
They couldn't multithread the components like compositor and renderer as much as they would have liked, even with all the caveats.
- array_key_first 1y ago> The issue Mozilla faced wasn't that it wasn't safer than C. It's that it was not safe enough for their needs. I would agree with this for most use cases. My main qualm is lumping together C and C++. It's like lumping together Rust and JS, because they're both memory safe. But Rust is WAY more safe. JS is, overall, an extremely footgunny language. In my view, the jump from C to C++ is about the same as the jump from Rust to JS, potentially even bigger.