|
|
|
|
|
|
by jjcm
1364 days ago
|
|
|
Big disclaimer that I work for Figma, so HEAVY biases here. In my eyes the 2GB/4GB limit for browser memory caps feels like an implementation issue rather than it being the wrong platform. At least for me, I value the ability to easily collaborate with people more than the need to have code be explicitly local or for things to be offline. The browser is excellent at that, and the explosion of online SASS products over locally installed apps in the last decade has shown it to be true for most use cases. I don't think it's difficult at all to imagine a web app "stably and efficiently growing to Swiss army knife-levels of capability". Increasing that per-tab memory limit feels like an easier hill to climb than finding a way to provide that instant access for everyone and collaboration baked into locally installed apps. Also don't kill yourself, even if it's a joke, life is more than software. |
|
|
I hear what you're saying, and definitely get how the sharing bit that has helped Figma take off like it has is good for the browser. I'm a bit at odds with the industry, though, in that that's probably one of the things I like least about Figma. But a lot of that is because I'm not always the best team player :].
I won't pretend to know enough about what goes into building these programs to say whether the RAM cap or native app collaboration is the more difficult thing to overcome, but it's clear to me that I would prioritize these differently from others.