Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Awesome work!

I noticed that the Servo Nightly build is already about as big as Chrome or Firefox. As it's not yet a complete browser, I expected it to have a lighter executable. Do you know what lead to this? Is it a matter of build artifacts or optimization? Is Servo going to grow even larger while achieving feature-parity with other engines?

It looks like Servo could be a great alternative for Chromium Content -- one of the things that keeps me from (ab)using Electron/NW/CEF is the massive initial overhead, and a WebRender-based UI with lower admittance price would change the whole scenario.



view as:

> I noticed that the Servo Nightly build is already about as big as Chrome or Firefox.

Probably not apples to apples. I don't believe optimizing for executable size to be too high in their priority list.


Legal | privacy