3 ms·
That tells us nothing about C++ vs Rust because the decision to use C++ for Zircon would have been made back in 2016 or 2015. At that time Rust was too immature
by magila 5y ago
That tells us nothing about C++ vs Rust because the decision to use C++ for Zircon would have been made back in 2016 or 2015. At that time Rust was too immature to warrant serious consideration for such a large project. More recently use of Rust in Fuchsia has been expanding, although the C++ kernel is obviously far enough along that they're not going to re-write it in Rust.
- oscargrouch 5y agoIts not just that. The experience of the teams also counts. For this kind of project its more important to have people with pratical experience in kernels, than experience in a particular language. These people will have a experience in languages they used before, so even if the decision was taken today, you wouldn't find enough people with experience in kernels AND Rust, but will have much more people with experience in kernels C and/or C++, so C++ would still be a good default in comparison to C. It would be pretty amateurish to get the kernel expert folks to learn Rust while implementing it, as it would probably mean that the end result in Rust would be worse than the end result in C++ as they were more comfortable and experienced in that language. It will take more time to form specialists in some key areas so that decision can be made with less side-effects.