Hey, huge fan and user of photopea. You are not far behind the VLC guy, u/jbk in my personal world view :)
If I may ask, if you were to do this all over again in 2024 - 2026, would you choose SSR?
Hey, huge fan and user of photopea. You are not far behind the VLC guy, u/jbk in my personal world view :)
If I may ask, if you were to do this all over again in 2024 - 2026, would you choose SSR?
Dumb q from someone who has done mostly native dev for…19 years, whoa.
Wouldn’t that screw up his whole thing? Because now you need infra to render to free users?
OK, so.. I get that, but isn't that model dead now? Doesn't this whole drama prove it? Aside from superior marketing, is there any way to protect an SPA from "Hey Claude, clean room this" in 2026 - and then apply better marketing - without even knowing anything about code?
As another example, ScreenRun is amazing as a true one-time pay, client-side app. I have loved that thing. Also, such a cool model to have no server costs. Whoever made that is also my hero. But are those days now over? Isn't an SPA now just basically open source, in the worst way only?
Meanwhile, Photopea only works via a website for normies. It is ad-supported, so given all the work put in, and updates, and the fact that it is web served... wouldn't SSR be a better option? (I hate this reality)
I swear I thought my question was not that dumb, or is it? You tell me.
yeah it would. an SPA is exactly what you'd want for a "webapp" like this, where you want everything loaded upfront so that you're mostly interacting with stuff offline. it's also very cache friendly so, really no benefit to using SSR.
SSR only really makes sense when you either want to optimize for fast page loads, or do PHP-style conditional rendering or whatever