Uther

Rewrite it in Rust has always been more a fantasy of the C++ community than a goal of the Rust ecosystem.

While compilation time is a well known Rust pain point, Rust error messages are really one of the best part of the language.

Complicated error messages are clearly no a common occurrence unless you rely heavily on meta-programming tricks, and that is not common in Rust, unlike C++.

You can already write kernel modules in Rust too.

The point is to integrate the Rust language to the Linux infrastructure so you can merge rust drivers to the official code base.

I'm not sure you can compare the code base of you first program in Go, that is probably small and straightforward, with something as huge and complex as Firefox.

The only real charset we should call ASCII is the 7-bit original standard. The 8-bits charsets are ASCII extensions.

While I would prefer brackets, that would not be enought to solve all the problems since, there would be conflict with array syntax too.

You have to be aware of this but most of the time this is not a problem. Most of the useless checks are optimized out, and if you suffer bound check performance somewhere in the program, and you know what you are doing, you can do unchecked indexing using an unsafe block with `get_unchecked()` .

Servo is a complete experimental standalone web engine. It only use the Javascript engine from Firefox (Spidermonkey).

Firefox is only using some parts of Servo : the graphic renderer (WebRender) and the CSS engine (Stylo).

It is not.

Go alone is easier than Rust. But since Rust has no GC, it is easier to embed, especially with a language with a Garbage collector like Python.

In this case the bug was only for a small subset of the Firefox users (Firefox without x264 support).

It doesn't seems impossible to me they missed this specific case.