8 ms·
Introduction to WebRender
- CoreXtreme 9y agoFirefox has fixed all issues for me. I am about to dump Chrome, just give me fast startup time.
- emerged 9y agoSince startup time is important, why don't browsers just stay running but pause all threads? The memory consumption of a browser process without any tabs open is insignificant for the vast majority of users.
- MarkSweep 9y agoGoogle Chrome does this, I think by default. It starts the browser process when you log in to your computer, so when you open a browser window it is really fast.
- panarky 9y agoI just checked Chrome Beta on Ubuntu, Windows and OSX, and there are no Chrome processes running upon login. No Chrome processes until I actually launch Chrome. Can you verify?
- solnyshok 9y agoit is a tick in the settings. something called "Continue running background apps.." in the settings-->advanced -- useful if you need google hangouts running in the background, or to get notifications from websites. I disable that though on all of my machines.
- kibwen 9y agoNote that WebRender won't be ready in time for Firefox 57 (yesterday was the cutoff for getting into 57), but the Servo devs tell me that it plans to be enabled by default in Firefox Nightly by the end of the year. So if you try Firefox 57 and find that it's still not as fast as you'd like, keep your eye out for when this lands early next year. :)
- Ygg2 9y agoI'm actually quite impressed with how Firefox Nightly is snappy. The only part missing, is Firefox slightly slower startup time (although that improved as well).
- infogulch 9y agoYes nightly is really fast and I'm really enjoying using it. But the missing extensions (mostly LastPass in my case) is starting to grind, even though a large number of extensions are already ported.
- nyordanov 9y agoI switched to bitwarden. I'm more worried about Tab Groups than LastPass.
- infogulch 9y agoRight. It looks like tree tabs is being ported too, which I'm glad about.
- Crespyl 9y agoI've reluctantly given up on Tab Groups, but losing VimFX and FireGestures is still causing me pain. TabGroups was really unique in that it felt (to me) like the kind of interaction-redefining change that tabbed browsing was in the first place. I'm adjusting myself to using virtual desktops and KDEs WM-level tabs to compensate, but I still miss the addon.
- 9y ago
- lostmsu 9y agoAfter reading the article, I still don't know what's new in WebRender
- Rusky 9y agoThat's intentional- this is "Part 1 - Browsers today."
- whowouldathunk 9y agoNot using the OS compositor locks you out of some cool stuff like backdrop blur and global lighting effects. At least on Windows, where both the native UI framework (XAML) and web platform use DirectComposition and thus can both benefit from it for effects and smooth scrolling. Which also means scrolling in apps can feel the same as scrolling in the browser. Disclosure: I work at Microsoft, not on anything related to graphics rendering or the compositor though.
- raphlinus 9y agoApologies if this is a derail, but how does DirectComposition compare to IDXGISwapChain1::Present1 for high performance scrolling and things like blinking a cursor with minimal energy usage? I was looking at the latter for the Windows port of xi-editor, and unaware of the former. I'm less concerned with fancy graphics effects, but perhaps if they're available at low cost I would consider using them. I'm also looking to optimize smoothness on window resize, which I've noticed to be pretty janky in many applications.
- pcwalton 9y agoNot using the system compositor for Web content doesn't mean you can't use it for OS integration: for example, WR could use DirectComposition to blend locally composited Web content over the desktop. As for scrolling, it is more work for us to match the OS scrolling behavior, for sure. But it can be overcome with effort and attention to detail. It's also important to note that adapting the CSS 2.1 Appendix E painting model to an OS compositor is itself an impedance mismatch. I wouldn't be surprised if WR's approach ends up being less code overall, simply by avoiding the need to shoehorn CSS into the OS compositor (which is also platform specific code). That's before you get into the large performance benefits you get from global optimizations like Z-culling, which generally aren't available when using the system compositor.
- modeless 9y ago> As for scrolling, it is more work for us to match the OS scrolling behavior, for sure. But it can be overcome with effort and attention to detail. You might think so. And yet, Android Firefox's non-native scrolling behavior continues to be totally awful. Has been for years. So many apps and websites fall into the trap of thinking that reimplementing OS scrolling is easy. I'm not saying it's the wrong decision, but know that you are signing yourself up for not just a ton of work now, but also a ton of work in the future to match platform changes.
- slezyr 9y agoHow you do multiple async http requests in rust? Last time I checked the only way do it was using tokio crate. But tokio is a huge mess and looked like Rust++. I.e. some language based on rust.
- steveklabnik 9y agoYou're being downvoted because this is quite offtopic for this thread; I suggest you post to https://users.rust-lang.org/ https://users.rust-lang.org/ for these kinds of questions.
- ekidd 9y agoThere's a ton of work being done at the compiler level to make Tokio more pleasant. This includes: 1. async/await. This is analogous to async/await in C# and ES6, and should make the syntax a lot nicer. https://github.com/alexcrichton/futures-await https://github.com/alexcrichton/futures-await 2. Coroutines. This is the supporting technology for async/await. https://github.com/rust-lang/rfcs/blob/master/text/2033-experimental-coroutines.md https://github.com/rust-lang/rfcs/blob/master/text/2033-expe... 3. 'impl Trait'. This provides a way to say, "Look, my return type implements 'Trait', but the actual type declaration is way to tedious to write out, and anyway, it's private. This will help a lot with cleaning up complex Tokio types. https://github.com/rust-lang/rfcs/blob/master/text/1522-conservative-impl-trait.md https://github.com/rust-lang/rfcs/blob/master/text/1522-cons... At work, we use Rust, but we're avoiding using Tokio until these features land.
- kibwen 9y agoI suspect you're being downvoted for being off-topic, consider asking on reddit.com/r/rust or StackOverflow.
- slezyr 9y agoI want response from Firefox/Servo devs. They need async http requests and they have experience in using those.
- 9y ago
- mozumder 9y agoNot sure how useful any of this will be without a full-fledged GPU-based font renderer.
- sp332 9y agoSkia isn't GPU-accelerated enough? It's what Chrome uses too right?
- yazaddaruvala 9y agoI'm sure the future blog posts will have more details, but it has to do with immediate mode vs retained mode APIs. https://www.youtube.com/watch?v=BTURkjYJ_uk https://www.youtube.com/watch?v=BTURkjYJ_uk
- robin_reala 9y agoYou’re in luck: https://pcwalton.github.io/blog/2017/02/14/pathfinder/ https://pcwalton.github.io/blog/2017/02/14/pathfinder/ As HN resident pcwalton says: “The immediate next step for Pathfinder is to integrate into WebRender as an optional accelerated path for applicable fonts on supported GPUs.”
- kibwen 9y agopcwalton is on the ball, as usual: "Pathfinder is a fast, practical GPU-based rasterizer for OpenType fonts" (and written in Rust) https://github.com/pcwalton/pathfinder https://github.com/pcwalton/pathfinder
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- binarycrusader 9y agoThey have one, but there's also Eric Lengyel's http://sluglibrary.com http://sluglibrary.com
- 9y ago
- noncoml 9y agoFirefox, please get your shit together and start focusing again on making a competitive browser again. Wanting to lead is good, but will not take you anywhere is no one is using your browser. All the other science project are not good, so please scrap them now.
- ubertaco 9y agoI'm interested in what you think it would take to "[make] a competitive browser again" if not major performance improvements.
- noncoml 9y agoPerformance improvements will not come magically just because they invented a new language and are re-writing everything in this language. I know I sound like an asshole, but it's only because I think Firefox is my last chance for a free web and am disappointed with the route it takes. I really wish they prove me wrong and in 2-3 years Firefox will be a marvel, re-written from scratch in Rust, but I am afraid that even if that's the case it will be too late.
- moosingin3space 9y agoThe goal of this series is to explain the techniques behind the performance improvements coming in WebRender. Additionally Mozilla is not re-writing anything from scratch, instead working toward integrating components from Servo into Firefox.
- pcwalton 9y ago> Performance improvements will not come magically just because they invented a new language and are re-writing everything in this language. Good thing that's not what's happening. None of the major Servo/Quantum features in question, including WebRender, are expected to be faster because they're written in Rust. Rather, they're expected to be faster because they've been designed from the ground up for modern hardware (in the case of Stylo, multicore CPUs; in the case of WR, GPUs).
- 9y ago
- bronz 9y agokind of a side note here, but the one thing, the one and only thing preventing me from uninstalling chrome is the fact that i need to use chrome to make google voice calls in the browser as far as i can tell. when i try to do it in firefox, i just get a strange message about it not being supported. this is really annoying!
- Manishearth 9y agoThis isn't something Firefox can fix, it's up to the Hangouts team to fix this.
- ksec 9y agoI vaguely remember, WebRender's idea came from some game developers, and those technique were then tested on a browser, resulting in 10-50x faster output. Unfortunately I cant google it to find out If i remember it correctly.
- Uther 9y agoI guess you are talking about https://air.mozilla.org/bay-area-rust-meetup-february-2016/ https://air.mozilla.org/bay-area-rust-meetup-february-2016/