[FractalHQ]

I had the same thought regarding the renderer — the worst case scenario would be a complex design with correct code that renders incorrectly in the app. I’d sacrifice frames per second just to avoid ever being in that position.

Regarding the text editor — I can’t stand using any editor that doesn’t have the hotkeys and multi cursor editing that I’m used to. I even stopped using note apps and just use vscode anytime I need to author more than a paragraph of text.

I worry that a clever image caching strategy and the Monaco npm package would be a better alternative for many reasons — especially considering the role that easy access to Devtools plays in the design process, which you also lose with a canvas.

[izakfr]

We agree that making the editor match the browser is super important. At some point we'll have implemented the whole CSS spec. Then, it should always match exactly.

Or at least we'll match Chrome. Sometimes browsers don't match each other.

[mappu]

Building a layout engine is, i think, most of the browser, in a world where we have extremely few browser engines. I'm sure you've got enough on your plate already but in your back pocket, maybe have a thought for running your renderer on standalone wgpu, throwing in V8 bindings, and becoming the next Ladybird / Servo?