Live data from Hacker News

Keeping Figma Fast: perf-testing the WASM editor

figma.com

41–50 of 99 posts

Re: Keeping Figma Fast: perf-testing the WASM editor

#41
post #11

Earlier quoted context omitted.

It would not. 1. Wasm based UI libraries exist already, checkout makepad [0] for example. 2. Web app standards are way higher than when flash was around. I highly doubt there would be any serious discussion that would also involve vue/react as alternatives. Almost as ridiculous as asking about using unity ui vs react. 3. Flash was world class media design tool for animation and production design. People were using it…

I do some graphics work and I wouldnt say that there is a world of difference between the capabilities of Illustrator and Figma. Photoshop is obviously a completely different tool. Very textural digital painting of the kind that photoshop excells at would be pretty tricky in a browser. (Theres a webversion of Heavypaint now, but thats vector-based of course.

Check out Photopea, it has a ton of features and is fairly performant in the browser. It also seemingly copies the UI of Photoshop but impressive nonetheless.

Re: Keeping Figma Fast: perf-testing the WASM editor

#42
I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab.

Then it takes a few seconds to load the file, which I don’t care much about.

But locking my entire browser is inexcusable.

It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

Re: Keeping Figma Fast: perf-testing the WASM editor

#43
post #42

I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab. Then it takes a few seconds to load the file, which I don’t care much about. But locking my entire browser is inexcusable. It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

I’ve seen this happen, but I don’t understand why that is possible. Chrome tabs are separate process, how can one tab freeze the whole browser even when running the worst code in existence?

Re: Keeping Figma Fast: perf-testing the WASM editor

#44
post #42

I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab. Then it takes a few seconds to load the file, which I don’t care much about. But locking my entire browser is inexcusable. It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

Requiring figma at a job should be a human rights violation :). I'm off the grid and whenever I use figma it drains my batteries with a high CPU load. I have to be careful to open it during the dead winter, if I leave it open I could drain my entire 5kw setup. If I throttle my CPU, it's totally unusable. Hopefully I can get a more efficent setup (currently an old 2400GE minipc). Usually I take a screen snapshot because this has happened.

Re: Keeping Figma Fast: perf-testing the WASM editor

#45

Evan Wallace (former CTO) was a WASM pioneer IMO, he has plenty of excellent explorations and works shared on GitHub. I don't know Evan, but I've greatly appreciated stumbling into his works when exploring SharedArrayBuffer and what was once bleeding edge browser performance. https://github.com/evanw

What do your mean? Did he contribute to the WASM standard?

Re: Keeping Figma Fast: perf-testing the WASM editor

#46
post #25

Earlier quoted context omitted.

I think Airbnb is the worst offender by far though. Instagram, Facebook and Twitter (just using your examples) operate very dynamic applications at a global scale. AirBnB is a crud app with almost no dynamic content other than the booking system. According to the first site I saw online, they process 6 bookings per second, which I could handle on literally anything with an internet connection. Of all of them, its the…

I thought this sounded way too low but the most generous figure I can find is 12 per second in 2022. What the hell? I thought it would be more. Should I have thought that? I guess not.

6 bookings per second at $200 per booking is $103M processed per day.

Each booking likely represents dozens to hundreds of requests. Then, for every visit resulting in a booking there’s probably hundreds of non-booking visits.

Re: Keeping Figma Fast: perf-testing the WASM editor

#47
post #42

I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab. Then it takes a few seconds to load the file, which I don’t care much about. But locking my entire browser is inexcusable. It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

I’ve seen this happen, but I don’t understand why that is possible. Chrome tabs are separate process, how can one tab freeze the whole browser even when running the worst code in existence?

Figma is beyond chrome, it's a quantum app: it's both in a state that will lock up my pc while everyone on zoom waits for the screen to load and a journey in following designer's instructions: "no a bit more left, no actually right, ok go down, no up, ok back go the left a bit, ok here it is!", same vibe as rally racing lol

Re: Keeping Figma Fast: perf-testing the WASM editor

#48

Evan Wallace (former CTO) was a WASM pioneer IMO, he has plenty of excellent explorations and works shared on GitHub. I don't know Evan, but I've greatly appreciated stumbling into his works when exploring SharedArrayBuffer and what was once bleeding edge browser performance. https://github.com/evanw

Former?! When did Evan step down?

Re: Keeping Figma Fast: perf-testing the WASM editor

#49
post #44
post #42

I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab. Then it takes a few seconds to load the file, which I don’t care much about. But locking my entire browser is inexcusable. It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

Requiring figma at a job should be a human rights violation :). I'm off the grid and whenever I use figma it drains my batteries with a high CPU load. I have to be careful to open it during the dead winter, if I leave it open I could drain my entire 5kw setup. If I throttle my CPU, it's totally unusable. Hopefully I can get a more efficent setup (currently an old 2400GE minipc). Usually I take a screen snapshot becau…

You're doing it wrong. What you need is a good exhaust on that mini pc; then you can use Figma as an inefficient heater during that dead winter.

Re: Keeping Figma Fast: perf-testing the WASM editor

#50
post #42

I have the displeasure of using Figma at my job. I have a very low opinion of anything that locks up my browser for multiple seconds (Chrome or Safari) whenever I open it in a tab. Then it takes a few seconds to load the file, which I don’t care much about. But locking my entire browser is inexcusable. It’s nice they’re working on performance once you get going, but launch performance is abysmal for me (x86-64 Mac).

I’ve seen this happen, but I don’t understand why that is possible. Chrome tabs are separate process, how can one tab freeze the whole browser even when running the worst code in existence?

Sounds like either processes are waiting on each other, or the OS sucks.
Post reply on HN