3 ms·
The Servo parts in FF is a CSS "engine" right? My expectation is that at some point it gets rewritten to C++ like the rest (layout, RT, API, fonts, parsing, JS
by tannhaeuser 6y ago
The Servo parts in FF is a CSS "engine" right? My expectation is that at some point it gets rewritten to C++ like the rest (layout, RT, API, fonts, parsing, JS, UI) because having a minor part written in Rust (with an extra build system, test framework, API bindings to maintain) is only a hindrance to building a team able to pickup work of other members. Especially when that other language has failed to deliver, and not even demonstrated the feasibility to develop a competitive JS VM, nor fast-enough binding to eg FreeType.
- steveklabnik 6y agoStylo, the component you're talking about, was written in Rust after multiple attempts to write it in C++, which all failed. So, I would hope that that isn't what happens. It sounds like a waste of time. > having a minor part written in Rust "every single CSS bit touches this code" isn't a minor part, and it's not the only part. https://4e6.github.io/firefox-lang-stats/ https://4e6.github.io/firefox-lang-stats/ is a sorta flawed metric but it reports nearly 10% being Rust.
- fulafel 6y agoWebRender is the biggest part in FF.