|
|
|
|
|
|
by Manishearth
2789 days ago
|
|
|
You're literally talking to one of the main initial people behind the Mozilla project that uses the GPU for browser rendering more than any other browser, on the comments of a post about this stuff making its way to a release. Webrender has a pretty large team working on it at this point. You have no idea what you're talking about here. |
|
|
I don't see how this vague appeal to authority adds anything to the conversation.
> Webrender has a pretty large team working on it at this point.
I guess what you're trying to say is that Firefox and Webrender in particular is a high priority for Mozilla. I would like to believe that this is true, but take a look at what Mozilla allocates its resources to[1] - Firefox Reality, Firefox Monitor, Pocket, ethics in CS, women who tech, etc. All fine and dandy, but the problem is that time is ticking for Mozilla Firefox.
Firefox is not even at feature parity with Chrome, never mind performance parity. For instance, I filed a bug[2] on bad input latency a whole year and 7 releases ago, and its still not fixed. A devtools bug for a websocket frames inspector[3] was filed 5 years ago, and its still not fixed either.
The time it takes to fix bugs and ship all these features is inversely proportional to the dedicated manpower. By the time Firefox reaches feature/performance parity with Chrome, it will have an insignificant single-digit market share, down from ~10.5% now. And that is with the incorrect assumption that Chrome will remain static.
[1] https://blog.mozilla.org/
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1408699
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=885508