Hacker News Reader

Comment by red023 | Hacker News Reader

Well yes I know that servo is about to make use of multi core but looking at its issues its far from ready for displaying websites correctly. So I am confused about this still as you have not really addressed what parts of servo are in fact in Firefox right now and what parts are not. I am not sure how "Rendering" is defined the way I understand it, its the part where servo has a looong was to go until its ready.

View on HN

Servo is still far from ready to use as a complete browser, but Servo is modular, and some modules are far more mature than others (intentionally so, because Mozilla wants to integrate those bits into Firefox ASAP, and so focuses most development there).

If you have the time there is a nice talk about WebRender: https://www.youtube.com/watch?v=BTURkjYJ_uk Here is another great talk: https://www.youtube.com/watch?v=an5abNFba4Q At ~25:30 he'll also talk a bit about Quantum.

In a nutshell WebRender is used to send a web page to the GPU which will paint all divs, borders, shadows, images etc. Currently WebRender is the only component I'm aware of that is inside Firefox Nightly. It's still behind a config though.

IIRC the first part to be used in Firefox is the URL parser: https://bugzilla.mozilla.org/show_bug.cgi?id=1151899

Note that the parser is off by default unless on nighty or aurora, and even in those cases it will run both rust-url and the regular parser to figure out what differences exist.

https://news.ycombinator.com/item?id=14167305

In nightly currently IPV6 urls are unconditionally serialized with rust code, and this will ride the trains to a release without being turned off.

Reply on news.ycombinator.com