Re:Rust required to build Gecko
by necessity on Friday December 16, 2016 @07:40AM
(#13192829)
Uh, yes, it is a big change, Rust is huge. I for one am dropping this bloatware for a WebKit browser once the changes hit Gentoo.
[ Parent
| on HN ]
Can you elaborate as to why Rust is bloat, and specifically how to achieve the goals of improved security and parallelism without using it?
V8 seems a bit more bloated to me than what comes bundled with Firefox.
Re:Rust required to build Gecko
by Matthias247 on Friday December 16, 2016 @08:29AM
(#13193065)
Maybe yes, maybe no. But Webkit doesn't use V8 anyway :)
True, I may have assumed they meant Blink, and something something Chromium, which breaking away from V8 isn't particularly easy, even if one is the CSS engine, and the other the JS engine. Sorry for leaping to conclusions.
But they may have meant Midori or similar which actually uses WebKit, through WebKitGTK+... Which means linking against GTK+, probably GTK+3 to get the main benefits like single-page not whole application crashing.
Which depending on your custom build, may or may not be an absolutely huge overhead.
It could be a tiny change to add to an OS. Or huge.
Do you realize this is a build-time, not run-time dependency?
Do you realize that Gentoo packages are distributed by source code rather than pre-built binaries?
Re:Rust required to build Gecko
by Manishearth on Friday December 16, 2016 @11:54AM
(#13194623)
FWIW last I checked Chromium took way more time and RAM to build for the first time from source. This was many years ago.
Except there are -bin packages there.
Re:Rust required to build Gecko
by disordinary on Friday December 16, 2016 @03:50PM
(#13196674)
I think once the transition to more rust components and parts of the servo project is complete the bloat will actually reduce significantly because Servo and all these libraries are built from the ground up without all the bandaids that have gone into decades of gecko development.