That's sad but sensical. Fun fact, Figma originally started as a fully C++ codebase, and Asm.js was key in proving that it would be possible to run a design tool in the browser. The switch to WebAssembly didn't happen until after there were paying customers, and provided nice improvements to load time (Asm.js is still JS which the bundle size is bigger and requires the code to be parsed into an AST, unlike WASM).

▲

0x457 2 hours ago | parent | next [-]

What's so sad about it? It was just a compilation target that made sense at one point in time. Its like being sad about i386-unknown-freebsd1 being dropped.

	▲	rudi-c an hour ago \| parent [-]
		Yes, I don't mean that it affects the present. Only sad in a nostalgia sense.

▲

frumplestlatz 2 hours ago | parent | prev [-]

What’s sad about that is we could have had a clean, native, desktop Figma application.

▲

rudi-c an hour ago | parent [-]

This is a lazy statement based on extremely vague handwaving about desktop v.s. web. It's not the 2010s anymore. Time to drop these generalities.

Users were migrating to us _from_ desktop applications. Collaboration was the key differentiator, but a less well known reason was that improved performance, including but not limited to the support of large design systems, was also a commonly cited reason among paying customers for migrating to Figma.

	▲	MBCook 15 minutes ago \| parent [-]
		Users still care. Desktop or collaborative is a false dichotomy. Desktop or performance is too. I get why you did what you did. It makes sense. But don’t think there aren’t people out here who HATE everything being shoved on the web with no desktop option. No, electron and PWA don’t count.