If you say so, I'll check out a new version and try it again. I've tried it a few weeks ago on linux.
> A large amount of CPU usage during initial pageload, on the other hand, is a feature, not a bug. Using more resources lets us get the page loaded faster, which not only shows you the page faster but also typically reduces power consumption since we can get the CPU into an idle state.
Large CPU usage slows down other apps - that's one reason why I use ff instead of chrome. 8GB RAM seems too few nowadays...
> Manual memory management isn't about some broad notion of "resource consumption": it's about having low-level control of resources, which can not only reduce memory usage but also eliminate pauses. I think it's very unlikely that the JavaScript garbage collector could be made thread-safe without regressing performance (which is what you presumably mean by "just use a GC").
I was pointing to the promise that it shouldn't leak while it seems to be doing it seriously.
> Just to name the first features that come to mind: Rust has a module system and hygienic macros, which are syntactic features not in C++. Rust comes with a standard library that includes networking, which isn't in C++.
I don't really like Rust's module system but +1 for the hygienic macros.
> Those "tweaks" are in fact likely to be slowing down your browser.
Have you heard about experimental features like pipelining and prefetch? Or content restrictors like uBlock and disconnect? Or session+history limits? When I reset my ff settings(due to ff profile problems) the vanilla ff takes at least 2x as much time to load the same page. If these "tweaks" wouldn't present - I wouldn't be a happy ff user.