Anecdote regarding this new FF: I would find frequent cases where my system would stall for 10-20s (could not caps lock toggle, pointer stopped moving). I almost always have just Chrome and gnome-terminal open (Ubuntu 16.04). I had attributed it to either a hardware or BIOS/firmware defect. Now, after switching to Firefox I have gone a week without seeing those stalls. YMMV -- I never bothered to investigate, it coul…
This sounds vaguely like what I've been experiencing on recent Chrome versions. On Windows I've had Chrome randomly hang... initially on the network, then after a few seconds even the UI freezes. When that happens, if I launch Firefox and try to access the network, it hangs too. But programs that don't try to access the network don't hang. Then after maybe (very roughly) 30 seconds, it all goes back to normal. No ide…
How Stylo Brought Rust and Servo to Firefox
21–30 of 199 posts
Re: How Stylo Brought Rust and Servo to Firefox
#22Re: How Stylo Brought Rust and Servo to Firefox
#23This is the most impressive, and useful aspect of all the recent work in Firefox. Rust is an amazing language. It really brings something new to the table with its borrow checker.
The fact that rust was created as part of a greater effort to work on a web browser is amazing.
Re: How Stylo Brought Rust and Servo to Firefox
#24Installed the new firefox, had 1 tab running for a few days which had allocated more than 10gb of virtual memory. I had high hopes but im sticking with chrome.
Re: How Stylo Brought Rust and Servo to Firefox
#25Congratulations, it's really an unparalleled performance of parallel performance.
I updated my developer version yesterday and it was as if Firefox - already ludicrously fast compared to before - turned on the turbo booster.
Obviously, I'm not complaining ;)
Re: How Stylo Brought Rust and Servo to Firefox
#26Installed the new firefox, had 1 tab running for a few days which had allocated more than 10gb of virtual memory. I had high hopes but im sticking with chrome.
Forgive my ignorance, but does having X amount of virtual memory allocated necessarily correspond to physical memory (and storage for that matter?)
Re: How Stylo Brought Rust and Servo to Firefox
#27Installed the new firefox, had 1 tab running for a few days which had allocated more than 10gb of virtual memory. I had high hopes but im sticking with chrome.
Forgive my ignorance, but does having X amount of virtual memory allocated necessarily correspond to physical memory (and storage for that matter?)
That said, even if the poster is correct, it isn't necessarily wrong either. AFAICT, nothing stops JS on a page from allocating that much memory, and "leaking" it (e.g., holding on to the JS object, maybe accidentally in a giant list, and not making use of it). It isn't the browser's fault if JS is actually "using" that much RAM.
Re: How Stylo Brought Rust and Servo to Firefox
#28> Stylo was the culmination of a near-decade of R&D, a multiple-moonshot effort to build a better browser by building a better language. This is the most impressive, and useful aspect of all the recent work in Firefox. Rust is an amazing language. It really brings something new to the table with its borrow checker. The fact that rust was created as part of a greater effort to work on a web browser is amazing.
Re: How Stylo Brought Rust and Servo to Firefox
#29Re: How Stylo Brought Rust and Servo to Firefox
#30It would be great to create the html/css/javascript stack from scratch, or at least make a non-backwards-compatible version that is simpler and can perform better. HTML5 showed us that can work.