Over the last year, we have gained a better understanding of the performance and correctness characteristics of the various rendering technologies available on the web, and have been experimenting with a second approach that uses CanvasKit. CanvasKit brings Skia to the web using WebAssembly and WebGL, enabling a hardware-accelerated drawing surface that improves our ability to render complex and intensive graphics efficiently.

WebAssembly is pretty great, but should web applications just be rendered to a canvas, and every application brings its own graphics toolkit? Do we really want anti-aliasing differences between web applications? Applications-in-containers is a thing - look at Qubes - but it’s not really something that users should want.

El jardín de la extracción capitalista se constru-ye mediante tecnologías de exterminio que acaban con la bio-diversidad natural y, por lo tanto, con la potencialidad actuante de la materia.

the idea as a ‘Theory of Ruin-Value’, henceforth taking care only to use building materials that would crumble picturesquely (Speer, 1969). I offer this uncomfortable story, like the irradiated Strahlenkatze of nuclear semiotics, as an instance of our common drive to communicate across millennia—whether we grasp the fact, or not, that what we speak may be our darkest sin.