3,691 karma · joined July 5, 2011
Both browsers use threads extensively within each process as well.
That's a comparison on real websites rather than browser benchmarks.
Also, Quantum Flow is not so small! It's actually now the part of Quantum that's getting the highest priority and most resources. It doesn't involved any single component, but is rather a focused effort to relentlessly profile Firefox on real-world workloads and eliminate as many noticeable slowdowns (jank, stutters, pauses, spinning beachballs, etc.) as possible. It's been hugely effective, with noticeable speed-ups in each release from Firefox 54 to 57. Ehsan Akhgari's blog has more details: https://ehsanakhgari.org/blog
http://searchfox.org/mozilla-central/rev/bbc1c59e460a27b2092... has some of the gory details.
"Set things up so that fatal warnings are off by default, but enabled on continuous integration (CI). This means the primary coverage is via CI. You don’t want fatal warnings on by default because it causes problems for developers who use non-standard compilers (e.g. pre-release versions with new warning classes). Developers using the same compilers as CI can turn it on locally if they want without problem."
Four is a reasonable default, especially given that multi-process is so new. It's possible that the default number may increase in the future, but that will depend heavily on memory usage.
I think the likely explanation is that Google is a large company with numerous departments and those departments don't always pull in the same direction. I imagine some people within Google weren't happy with the Google Earth announcement.
Here's an old blog post describing it, by DHAT's author: https://blog.mozilla.org/jseward/2010/12/05/fun-n-games-with...
Here's another blog post in which I describe how I used it to speed up the Rust compiler significantly: https://blog.mozilla.org/nnethercote/2016/10/14/how-to-speed...
And here is the user manual: http://valgrind.org/docs/manual/dh-manual.html
That's exactly right. The amount of Flash content dwarfs the amount of other plugin content.
Banning other NPAPI plugins doesn't avoid the Flash security problems but it does avoid the other security problems. It's a step forward, but it's not the final step.
Really? Why is that?
#include <stdio.h>
int main(void) {
printf("hello world\n");
return 0;
}
Rust: fn main() {
println!("hello world");
}Can you give an example? I'm sure Mozilla's animation people would love to hear about this.
(You could probably replace "move semantics" in that sentence with multiple other C++ features and still have a valid statement.)