51–60 of 99 posts
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?
I don't really know what any of this means. You're running a single-thread graphics API (OpenGL) in a browser (does WASM support background threads?). On any modern PC, that's gonna look like 1 CPU thread doing all the work and the GPU idling 80% of the time waiting for something to happen.
Nice post. Figma's engineering blog looks great; right up there with Airbnb's and Etsy's which I also enjoy.
No RSS feed though afaict :(
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?
Because if anything takes up 100% of CPU, other things starts being unresponsive as there is not enough CPU to go around. Happens easily when dealing with concurrency and parallism, which I'm guessing Figma happily uses.
Earlier quoted context omitted.
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?
> 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? Because if anything takes up 100% of CPU, other things starts being unresponsive as there is not enough CPU to go around. Happens easily when dealing with concurrency and parallism, which I'm guessing Figma happily uses.
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).
Figma is anything but fast. Whenever I need to open a file it takes a minute to load on my half a gigabit connection. It's strange how much people are willing to put up with slow software nowadays.
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…
The computer you mentioned comes with a 65 watt AC/DC converter which should last 77 hours minimum on a 5kw battery.
Then there is the nonsense about blaming a web page for not having enough power after choosing to do a tech job while living off a battery.