nicalsilva

5 ms·

1.
by nicalsilva 2y ago
Firefox's user base is also full of old Intel integrated GPUs that don't support bindless. The day WebRender can start relying on it cannot come soon enough but it's a long way off.
2.
by nicalsilva 2y ago
(I'm the author of the blog post) Yes, WebRender could repack it's texture atlases. A lot of stuff of various sizes go in there so I would not want to rely on repacking large amounts of pixels frequently but it could, among other
3.
by nicalsilva 9y ago
It's a matter of allocating time to implement the missing parts and get it to work properly. Right now the people who could do this are working on other things but it will get done eventually.
4.
by nicalsilva 9y ago
As pcwalton said, there is a whole lot of things on the web that are very cheap to render on a GPU if done right. For these things, a well tuned gpu renderer can easily outperform a naive compositor like what you can see in most browsers. A
5.
by nicalsilva 9y ago
Actually, Gecko's compositor knows the screen space invalid region and scissors out the rest when compositing. The invalid region is passed to the window manager. Chromium also does that although they settle for an invalid rect instead
6.
by nicalsilva 9y ago
It depends. For a lot of web pages, the things webrender do are actually very simple and can be faster than Firefox's compositor even if there was no painting required. The expensive stuff like rasterizing glyphs are cached. The idea i
7.
by nicalsilva 9y ago
Let's clarify, WebRender doesn't do anything at all if nothing changed. If the content of the window is static then webrender won't wake your gpu up until it really needs to. There seem to be a confusion about video games nee
8.
by nicalsilva 11y ago
What? Whether or not a browser matters depends on the amount of people using it, not on whether you can install it on several operating systems.
9.
by nicalsilva 11y ago
I find that gtk3 themes are easy to tweak (and more so than gtk2 ones), have you tried to look at the (pseudo-)css and modify it to suit your taste?
10.
by nicalsilva 11y ago
Firefox uses GTK to draw native-looking widgets. Basically, Gecko passes an X11 pixmap to GTK2 the latter draws the buttons/scroll bars/etc. into it with xrender. This means that Firefox either has to do all of the rendering with
11.
by nicalsilva 14y ago
Sure! This post is like an invitation to discuss the subject, right? "over-engineering" was not the point anyway. The title is a lie. The point was: dont be afraid of making mistakes (Over-engineering and the likes) when you can afford to,
12.
by nicalsilva 14y ago
I don't know about this particular series of comments, but I second him on the idea that often some comments on HN smell like "If I troll harder I'm gonna look cooler". It somewhat degrades the overall quality IMO.
13.
by nicalsilva 14y ago
For what it's worth, the rubber band thing having a patent on it, I am not sure shipping it in Firefox is only about implementing it. I do know sometimes patches wait in bugzilla for legal approval, and I do know implementing native-like fe