It's also worth mentioning that Mozilla tends not to use a lot of standard C++ types, using nsTArray instead of std::vector or nsA?C?String instead of std::string. This makes the porting of APIs using arrays or structs easier, since Mozilla owns the ABI rather than needing to worry about different standard libraries having different ABIs.
C++ interop with C++ can be a pain. E.g. even with the same version of the same compiler, GCC can have different options enabled that affect the layout of some types.
That is the same in all languages mature enough to have variant options. Rust included.
Therefore, a tendentious distraction from the topic. Chris, I shall expect better from you in the future.
Looks like the Chromium team could also snag a few of them, since servo team is axed