News for hackers. Stuff that matters.
Re:Vibecoding Photoshop: Time and pressure by lewelove on Tuesday October 06, 2026 @08:23PM (#49986182)
Never got to try out PhotoSuite, looks like it really was just ripping-off your code, the repo owner already deleted it, and now it forks PhotoCraft.

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.

Re:Vibecoding Photoshop: Time and pressure by IvanK_net on Wednesday October 07, 2026 @02:24AM (#49989051)
Thanks a lot!

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.