RenderingNG: An architecture that makes and keeps Chrome fast for the long term

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • gpuweb

    Where the GPU for the Web work happens!

  • typometer

    Text / code editor typing latency analyzer

    open -a Spotify --args --disable-smooth-scrolling

    You used to be able to disable Chrome's smooth scrolling with chrome://flags/#disable-smooth-scrolling, but that flag was removed for whatever reason.

    I'm also surprised by how much faster Firefox's builtin middle mouse click autoscroll is compared to Chrome's ersatz AutoScroll[2] extension.

    [0]: https://download.developer.apple.com/Developer_Tools/Additio...

    [1]: https://pavelfatin.com/typometer/

    [2]: https://chrome.google.com/webstore/detail/autoscroll/occjjkg...

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  • play-with

    WebExtension to open a video stream on a web page with an external player.

    Over the past ~10 years, I've come to the conclusion that it's best to just pipe high quality video streams into a high quality cross-platform external video player like mpv[0][1][2].

    I can't remember what Firefox uses internally to decode/display different video codecs (ffmpeg like mpv? system builtins? hardware media encode/decode, like on the M1?)

    I can't put my finger on exactly why browser video streams feel so bad to me, but they still do. Maybe it's the DOM overhead, or maybe it's something else. My personal takeaway is that browsers still just aren't optimized enough for fast/performant video playback.

    [0]: https://mpv.io/

    [1]: https://github.com/grmat/play-with

    [2]: https://addons.mozilla.org/en-US/firefox/addon/play-with/

  • mpv

    🎥 Command line video player

    Over the past ~10 years, I've come to the conclusion that it's best to just pipe high quality video streams into a high quality cross-platform external video player like mpv[0][1][2].

    I can't remember what Firefox uses internally to decode/display different video codecs (ffmpeg like mpv? system builtins? hardware media encode/decode, like on the M1?)

    I can't put my finger on exactly why browser video streams feel so bad to me, but they still do. Maybe it's the DOM overhead, or maybe it's something else. My personal takeaway is that browsers still just aren't optimized enough for fast/performant video playback.

    [0]: https://mpv.io/

    [1]: https://github.com/grmat/play-with

    [2]: https://addons.mozilla.org/en-US/firefox/addon/play-with/

  • three.js

    JavaScript 3D Library.

  • WHATWG HTML Standard

    HTML Standard

    TBF even the spec authors are a bit confused about that attribute: https://github.com/whatwg/html/issues/5466

    It has complex and non-obvious effects. greggman on the three.js issue wrote a really nice summary on why it shouldn't be the default.

    It's really only appropriate for highly latency sensitive applications, like drawing or certain games.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts