(Replying to PARENT post)
I believe Figma is indeed written in C++ and uses emscripten. It's pretty much the polar opposite of your standard CRUD app.
Old article: https://www.figma.com/blog/webassembly-cut-figmas-load-time-...
👤grose🕑1y🔼0🗨️0
(Replying to PARENT post)
The existing C++ Photoshop codebase was largely ported to WASM with Emscripten https://web.dev/articles/ps-on-the-web
👤chilli_axe🕑1y🔼0🗨️0
(Replying to PARENT post)
I tend to dislike this approach for the simple reason that it's an extra "compatibility layer" where you give up control. If you're developing for the web you may every now and then want to do things a specific way or use a specific feature and be unable to do so because the transpiler doesn't support it or is programmed not to.
👤lacerrr🕑1y🔼0🗨️0
(Replying to PARENT post)
Why? If there's one thing JavaScript and browser tech is good at, it's making GUI dev easier. Just look at how even Qt is basically pivoting completely towards QML which to my naive eyes look very very similar to how GUI/Layouts/styling is done with html5/Js. Why would you purposefully use something worse just to not use browser related tech? I would agree if this was about raw number crunching, where compiling to wasm makes sense and where a html5 GUI can be used as a frontend, but the GUI itself has no reason to be built with CPP.
👤mardifoufs🕑1y🔼0🗨️0
(Replying to PARENT post)
I don't think that workflow was even a realistic option when Figma development was initiated, or even when it first launched.
👤diggan🕑1y🔼0🗨️0
(Replying to PARENT post)