Slashdot Mirror
Mozilla Enables WebRender By Default On Firefox Nightly
RoccamOccam writes: WebRender, an experimental GPU-based renderer for web content, written in Rust, is now enabled by default for Firefox Nightly users on desktop Windows 10 with Nvidia GPUs. The announcement was made on the mailing list.
Lin Clark provides an excellent overview of WebRender and, states, "with WebRender, we want apps to run at a silky smooth 60 frames per second (FPS) or better no matter how big the display is or how much of the page is changing from frame to frame. And it works. Pages that chug along at 15 FPS in Chrome or today's Firefox run at 60 FPS with WebRender.
In describing the WebRender approach Clark, asks, "what if we removed this boundary between painting and compositing and just went back to painting every pixel on every frame? This may sound like a ridiculous idea, but it actually has some precedent. Modern day video games repaint every pixel, and they maintain 60 frames per second more reliably than browsers do. And they do it in an unexpected way instead of creating these invalidation rectangles and layers to minimize what they need to paint, they just repaint the whole screen."
Lin Clark provides an excellent overview of WebRender and, states, "with WebRender, we want apps to run at a silky smooth 60 frames per second (FPS) or better no matter how big the display is or how much of the page is changing from frame to frame. And it works. Pages that chug along at 15 FPS in Chrome or today's Firefox run at 60 FPS with WebRender.
In describing the WebRender approach Clark, asks, "what if we removed this boundary between painting and compositing and just went back to painting every pixel on every frame? This may sound like a ridiculous idea, but it actually has some precedent. Modern day video games repaint every pixel, and they maintain 60 frames per second more reliably than browsers do. And they do it in an unexpected way instead of creating these invalidation rectangles and layers to minimize what they need to paint, they just repaint the whole screen."
Only LUDDITES use WebRender. Modern app appers use AppApper!
Apps!
It's not your computer.
https://www.youtube.com/c/BrendaEM
Quite the opposite. If there is no invalidated states on the screen, no painting occurs. It only paints when it needs to. It actually consumes less power overall because of the amount of code that is required to handle invalidation of only parts of the screen is massively slow. This is why the browser renders so much faster. Instead of 200ms per paint of a small section of the screen, it renders the entire screen in 15ms. The rest of the time, your CPU/GPU sits idle. Also, Webrender does all rendering on the GPU instead of CPU, so it has better optimization for painting the scene (CPUs suck at this entirely)
Any plans to target 120 Hz?
Lin Clark provides an excellent overview of WebRender and, states, "with WebRender...."
I have no idea why I typed all of those commas.
win 10 3d animated fonts to the rescue!!!
Even better, take out the Google spyware links. (Google is far from the only culprit, they just waste the most total time.)
When all you have is a hammer, every problem starts to look like a thumb.
Firefox is my main browser for a lot of reasons, not just that Google doesn't dominate it. Great to see the Mozilla team leading the way on this, and it's a big validation for Rust. Any serious systems programmer ought to take a close look methinks.
When all you have is a hammer, every problem starts to look like a thumb.
Don't program for a web browser.
Or stop people from filling up their sites with bullshit JS and media.
The millennial that doesn't like most of the stuff designed for millennials.
Sure thing, buddy.
There you go.
#DeleteFacebook
How's life in the hypocrite lane?