3 ms·
It is hilarious that the big insight here is “there’s got to be some hidden reason why Adobe is taking this defensive move.” It’s only hidden if you haven’t sp
by sirspacey 4y ago
It is hilarious that the big insight here is “there’s got to be some hidden reason why Adobe is taking this defensive move.”
It’s only hidden if you haven’t spent any time googling Figma’s founder - who stated from Day 1 that multiplayer design is possible in the cloud and it can’t be file based.
Adobe needs Figma to replatform everything they have into that model, because they can’t abandon the tech stack they have.
The amount of value this is going to create isn’t a multiple on Figma’s revenue, it’s a multiple on Adobe’s.
- tadfisher 4y agoThey can't build multiplayer for less than 20 billion USD?
- llamaLord 4y agoWhat you have to understand is that Figma has some seriously bad-ass tech under the hood which is what makes their product possible. The reality is, nobody other than Figma is actually doing the whole “build a native C++ app and then compile it to WASM” thing that Figma does to the same degree, and it’s exactly the tech adobe needs to bring all their existing products to the browser properly. Adobe isn’t buying Figma, adobe is buying their web rendering engine.
- pjmlp 4y agoAdobe already has Photoshop running on the browser, and many of the WebAssembly improvements were driven by collaboration between them and Google, see Sean Parent talk at CppNorth 2022.
- andrei_says_ 4y agoI think Adobe is also buying Figma’s current, and future, users. Envisioning them as creative cloud subscribers.