News for hackers. Stuff that matters.
Re:What’s Next for Multi-Process Firefox by garaetjjte on Wednesday August 03, 2016 @04:26AM (#12216482)
Servo is written in Rust. That isn't going to improve performance.
Re:What’s Next for Multi-Process Firefox by Sylos on Wednesday August 03, 2016 @04:47AM (#12216573)
It should improve performance in the sense that Rust helps to produce code which can be easily parallelized.

But Servo being written in Rust isn't the argument that he's making.

Servo is built with a modern architecture, which all current browsers don't have, because they all started out somewhen pre-2000, before multi-core processors were really a thing, and before the web was really graphical.

What Servo can improve is mainly, that the rendering of HTML itself is parallelized in Servo, and that with WebRender, they utilize graphics cards quite similar to the way that videogames do it, which both do result in noticeable performance improvements.

Re:What’s Next for Multi-Process Firefox by Illniyar on Wednesday August 03, 2016 @05:09AM (#12216675)
Your comment implictly assumes that the programming langauge has a major impact on browser performance.

My expierence with other product development tells me otherwise, and I trust that the people behind mozilla who are specifically building a more performant browser using rust are aware of what does or does not greatly affects performance.

Re:What’s Next for Multi-Process Firefox by yoklov on Wednesday August 03, 2016 @05:20AM (#12216717)
That's not the only difference, or even an important one for performance. Servo's WebRender engine gets 60fps (or in the hundreds if uncapped) on many pages where Chrome, Firefox, Edge, etc. all struggle in the 5-15fps range.

(Of course, Servo is still a long way from production ready).