Showing the old engine as a graph that plummets, and the new one as one that doesnt, or the one that plots "frustration" against "features & complexity", is just utterly meaningless to me. Maybe this appeals to the small part of the community that gets excited for quirky and cool posts by big corps, but I only see about 5 paragraphs of info here.
Basically RenderingNG will more reliable and better and better and more reliable, and thats neat, I just wish they didnt waste so much of the reader's time.
Let's hope that the next post will have more meaningful technical content..
> Now look at the web. It's unusable without an ad blocker.
Don't like ads? Don't visit sites that run ads. For instance, I can't read most of online newspapers because of the ads; so I just don't bother. I visit HN instead.
> The tech mafia keeps tracking people and censoring the web, practicing right-speak and removing critical voices.
I don't know what right-speak is (is it speaking correctly or speaking on right-wing political topics?), but:
- peer-to-peer technologies exist (Odysee, Bitchute, etc.; still relying on the browser to work)
- less censorious networks exist (e.g. locals)
- you can self-host your own platform where you set the rules (phpBB, mattermost, etc.)
- you can run your own blog ang right-speak there to your heart's content; and maybe if this right-speech in interesting, you can attract commenters to exchange ideas (if you find this valuable)
Out of the box, Firefox has terrible rendering performance, not to mention hw-accelerated video decoding. Now, Chrome is not a whole lot better out of the box, since it still applies old "Driver bug workarounds" that have long been fixed in mesa/GPU drivers, but this is easy to circumvent with the `--disable-gpu-driver-bug-workarounds`.
I've been running Chromium with the said flag for over half a decade now, and I have yet to see one of the bugs manifest. Firefox on the other hand, has a similar entry in `about:config`, but one needs to tinker with even more flags to get Firefox to acceptable performance (Somehow, enabling xrender makes WebGL fast, but makes video decoding have weird jitter, etc).
The day Firefox gets comparable WebGL/video decode performance will most likely be the day I switch.
All you need is gfx.webrender.all, if you even failed the qualification (most modern setups shouldn't fail it).
How is this not #1 priority to fix?
I've used an addon for a while which fixed it by forcing YouTube to serve h264 rather than vp9 content, as hardware accelerated decoding of h264 worked but not vp9. But lately it hasn't worked well. Haven't investigated if it was due to newer content only being vp9 or if the addon stopped working.
Firefox does use Skia though.
That's why all this threaded rendering stuff sounded familiar. Mozilla putting massively-parallel Servo features into Firefox is already a few years old: https://en.wikipedia.org/wiki/Gecko_(software)#Components
I don't know if there's such a thing as an "NG site", and if there is, the new software will still support normal sites
As long as Safari is still around to haunt us, I think I will :)
