Re:The CSS Behind Figma
by 88913527 on Saturday July 23, 2022 @10:41PM
(#32209785)
Figma is getting too slow. Open browser tab, get a cup of coffee slow. Love what they did for the space and solutions they unseated, but they are mildly losing their edge.
[ Parent
| on HN ]
Are you using Mac? I've seen noticeable performance issue in past few months on my 4 year old Mac Book Pro.
However, it seems to just run on my 9 year old 3570 corei5 windows.
Maybe it’s just because I’ve been using an M1 MacBook Pro but figma absolutely flies for me without any hiccups.
It's time for WASM and Rust. DOM tools can render to their own optimized GPU-accelerated canvas and ditch DOM outright.
Re:The CSS Behind Figma
by cercatrova on Sunday July 24, 2022 @12:42AM
(#32210394)
Figma already uses WASM and Rust.
> DOM tools can render to their own optimized GPU-accelerated canvas and ditch DOM outright.
This is literally exactly what Figma does.
The big worry I have about this sort of approach is canvas accessibility. It's something the company also seems to be worried about - they put out a statement a couple of months ago about their plans to address accessibility issues going forward - https://www.figma.com/blog/a-step-forward-in-our-accessibili...
Furthermore it’s the only very popular app I know of to do that
Re:The CSS Behind Figma
by leodriesch on Sunday July 24, 2022 @08:08AM
(#32212640)
Google Docs also does that [0].
[0]: http://workspaceupdates.googleblog.com/2021/05/Google-Docs-C...
Lichess, Adobe XD, several Google products. Probably more I’m forgetting.