4 ms·
I fail to understand why not use the native browser rendering engine, or at least SVG for the UI. It must be cheaper in resources (memory, network, cpu), easier
by iddan 3y ago
I fail to understand why not use the native browser rendering engine, or at least SVG for the UI. It must be cheaper in resources (memory, network, cpu), easier to make accessible and easier to render
- jjcm 3y agoAnecdotally, in the very early days Figma rendered its UI entirely in canvas, but we eventually switched over to React for the UI. It ended up being far easier for development cycles and for accessibility/integration with existing browser features.
- solardev 3y agoI thought you guys recently rewrote everything to be in WebGL instead?
- rileyphone 3y agoGo inspect the source and see for yourself, the UI is normal HTML.
- pests 3y agoI think their UI is react but the actual drawing canvas is WebGL.
- TrevorSundberg 3y agoI always thought it was so cool Figma just rendered to a canvas! Oddly enough I ran into this at my previous job doing browser isolation when we got a bug report that Figma wasn’t displaying properly in our browser. Makes sense to switch the rest of the UI to react though, just for how many people know it.
- TrevorSundberg 3y agoThe main reason was just because this engine was entirely built for native platforms originally in C++ (not for the Web). This is a port, hence why the UI is running in WASM/WebGL.