It was discussed here on HN yesterday and then, the anonymous person behind it removed the "Issues" section completely from their Github
https://news.ycombinator.com/item?id=49972730
https://replayweb.page/?source=https://archive.org/cors/gith...
It was discussed here on HN yesterday and then, the anonymous person behind it removed the "Issues" section completely from their Github
https://news.ycombinator.com/item?id=49972730
https://replayweb.page/?source=https://archive.org/cors/gith...
I have a huge respect for your work on Photopea, been using it constantly since the time I completely moved to Linux a year ago. It has the best Photoshop parity yet to find! Would you ever consider to: 1. Open sourcing your work (partially or completely) under some kind of a permissive/copyleft license. 2. Rewriting some parts of the website that require performance as WASM targets. 3. Using any modern JS frameworks, e.g. Svelte.
1) About 30% of my original code is open-source as JS libraries: they end with ".js"-https://github.com/photopea?tab=repositories
2) WASM is not faster than Javascript "by default". Both can be fast or slow depending on how you write it. I don't think having everything in WASM would make Photopea significantly faster. Also, Photopea uses many libraries as WASM (WEBP decoding, ZSTD decoding, JPG decoding, Harfbuzz, ... JXL / AVIF encoding)
3) I never used any Framework, but if it is just a bunch of a JS code, I think I managed to write an equally good JS code for the UI over the past 14 years.
Can you settle an argument, perchance? Is it pronounced "Photo-P" or "Photo-pia" (as in "utopia")?
I had settled on the utopia sounding version but will try and think of peas now.
If I may ask, if you were to do this all over again in 2024 - 2026, would you choose SSR?
Wouldn’t that screw up his whole thing? Because now you need infra to render to free users?
SSR only really makes sense when you either want to optimize for fast page loads, or do PHP-style conditional rendering or whatever
As another browser example along the lines of Photopea, ScreenRun is amazing as a true one-time pay, client-side app. I have loved that thing ever since I paid the $50. Such a cool app and model that has no server costs. Whoever made that is also my hero. But aren't those days now over? I guarantee there are >100 ripoffs of it now. Isn't an SPA now just basically open source, in the worst way only?
Meanwhile, Photopea.com 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)
edit: I am allergic to Next, so I have been using Sveltekit since I realized that SPAs are now accidental open source. What have others been using for SSR and why? That is the discussion I would really like to have.
I guess my point was, how can anyone protect any client-side IP in the modern era?
And at 8 Euro a month I can't quite justify the Photopea premium plan.
I use it enough I would happily pay say $50 for a self-hosted single user license that will not get updates. But not 8 euro a month forever.
I am finally forcing myself to un-learn the decades of Adobe muscle memory and replace it with gimp/krita. Or maybe I'll vibe up something that does exactly what want and nothing more; bespoke one-off tooling is just so easy to do now.