Forking Chrome to render in a terminal (2023)
1–10 of 20 posts
Re: Forking Chrome to render in a terminal (2023)
#2Re: Forking Chrome to render in a terminal (2023)
#3Re: Forking Chrome to render in a terminal (2023)
#4This is really, really cool!
Skia is a incredible abstraction layer. The linked article at the top of the OP https://fathy.fr/html2svg (2022) has some great graphics of how Skia can support various backends including PDF rendering (via https://skia.org/docs/user/sample/pdf/).
It's also worth noting that the Chrome Graphics team is writing yet another Skia rasterization backend, just announced last month: https://blog.chromium.org/2025/07/introducing-skia-graphite-...
Given that this article came out a couple years ago, it's quite possible that it was seen by the Chrome team and inspired them to look at making a new backend from scratch!
Re: Forking Chrome to render in a terminal (2023)
#5Re: Forking Chrome to render in a terminal (2023)
#6Carbonyl is surprisingly performant and usable, especially with --zoom=300 --bitmap
At lower resolutions, it would be nice to render images using a "subpixel" terminal rendering library like chafa (https://hpjansson.org/chafa/), or maybe sixels/kitty image protocol.
Re: Forking Chrome to render in a terminal (2023)
#7Wow, that's crazy. I also had never heard of Mojo before. Reminds me of Microsoft COM.
https://chromium.googlesource.com/chromium/src/+/refs/heads/...
Re: Forking Chrome to render in a terminal (2023)
#8No need to render to ASCII/Unicode anymore!
Re: Forking Chrome to render in a terminal (2023)
#9"Forking xterm to render graphical applications"