Photopea creator weighs in on Photosuite project
github.com/eolix
[3 comments hidden]
The hard reality though is any site written in JavaScript is now part of an LLM's training set and can (and will be) be trivially rewritten into something new. Interesting times.
>“He who hath grown wise concerning old origins, lo, he will at last seek after the fountains of the future and new origins. […] For the earthquake—it choketh up many wells, it causeth much languishing: but it bringeth also to light inner powers and secrets. The earthquake discloseth new fountains.”
— Nietzsche, Thus Spake Zarathustra
[10 comments hidden]
[8 comments hidden]
It makes a lot of sense architecturally. It's much simpler to update a webpage than force every user to update their app when something needs to change. Consequently a lot of apps, especially on mobile, use a system webview with a page loaded from a server and rendered to look like the app for anything that gets regular updates. The alternative is having lots of versions of the page and needing to manage all the different variations of payloads from them.
Backwards compatibility in an API isn't that hard, but when there's a simpler option (a webview) people will take it.
That said, if there's no native stuff in the app, it is a bit harder to justify.
[hidden]
[2 comments hidden]
This kind of thinking is what brought us the trend of painful Electron apps like Teams.
[3 comments hidden]
The set of capabilities available to native desktop apps is a superset of the capabilities available to browser-based Web apps.* Ergo, if browser-based app distribution possesses some desirable quality, the same path is available** to a native app not built on W3C/WHATWG APIs.
* You can frequently come across people make a similar logical error in the opposite direction when it comes to being more distrusting of browser-based apps than native binaries, especially with an undue focus on the risk of the app exfiltrating your data over the network—even though a native binary can do strictly more damage than a browser-based app, which is at least confined to its sandbox and the associated execution model.
** It does require, though, that one actually take that path.
[2 comments hidden]
Not a logical error. A notarized or app store app can be blocked from accessing the network so there is no data exfiltration happening. The malware risk is negligible thanks to Apple’s vetting.
[hidden]
That much is true, but I consider this misfeature a clear disadvantage for the customers using the app, which are at the mercy of the developer. The days of updates being something positive are long gone. Nowadays they’re a mix of UI redesigns requiring relearning stuff, spyware, unwanted bloat, bugs and a couple of actually useful things thrown in.
[hidden]
[18 comments hidden]
[4 comments hidden]
So that did not work out, but I used it a bit and interacted with him couple of times there, before moving on to easel and later pixi, after it became clear it would not take off and the other ones had more support.
Glad for him to found success with Photopea later, and he definitely has my sympathy here.
But I doubt this will work out much longer in the long run. It is just too easy cloning and improving projects with AI.
[7 comments hidden]
[2 comments hidden]
[hidden]
[hidden]
[2 comments hidden]
Photopea is not, and has never been open source, AFAIK.
[9 comments hidden]
[7 comments hidden]
[hidden]
[5 comments hidden]
Archived at: https://web.archive.org/web/20261006025310/https://github.co...
[hidden]
[24 comments hidden]
the future of software is oss. unless governments lock down access to these tools to prevent this kind of reverse engineering. which is a horrible future to envision.
[1] https://github.com/vladtrc/iw4L
[2] https://www.youtube.com/watch?v=9UbADrcEW5w
[3] https://github.com/chasmlol/2010-rust-rewrite-mashup
[4] https://www.reddit.com/r/bevy/comments/1wuu7bx/are_you_seein...
[5] https://www.reddit.com/r/bevy/comments/1wuag9d/skate_3_was_r...
[13 comments hidden]
[12 comments hidden]
[6 comments hidden]
[5 comments hidden]
By that standard, couldn't I say you don't truly own open source software like Chromium or OpenSSL because very few are capable of understanding the codebase well enough to implement changes?
[4 comments hidden]
And there's a difference between few being capable of implementing changes, and anyone. In a world where most or all code is written and edited by LLMs, and CS courses are focused on how to prompt LLMs and no longer on fundamentals, the opportunities for humans to learn programming will all but vanish. And this assumes LLMs will even expose code at all. They may simply emit precompiled applications in the future. If humans remain in the loop even when LLMs are used then this becomes less of a problem. But the culture around LLMs converges on vibe-coding - as little direct human understanding or effort as possible. As such it converges on sacrificing freedom for convenience.
[3 comments hidden]
Last week, I've seen videos of people merging video games like Super Mario and Minecraft to create absurd new games that previously you wouldn't imagine anyone implementing because the cost/effort was prohibitive.
[2 comments hidden]
No, because they aren't modifying the software, a proprietary service is modifying the software. The freedom belongs to the company owning the LLM, not the person using it. If the freedom belonged to the person using it, then they would be able to exercise that freedom without an LLM. As they cannot, they did not in any way gain freedom by using the LLM.
If you think remixing games using an LLM is cool, I don't want to take that from you. It just isn't FOSS. The wholesale contempt that so many AI users have for human coding demonstrates that it's an entirely different culture with different ethics and different goals.
[hidden]
Personally I enjoyed building apps before AI, and have been doing so professionally for 10 years.
With AI it's much more fun for me since productivity is way up.
It's not that I have contempt for human coding, I just know from my own experience and hard work that using AI is much more productive.
People online constantly make comments where they insult my expertise and the quality of what I am building. Surely you can see how this could quickly lead to a heated discussion.
[5 comments hidden]
[hidden]
- the software would run only on your own server and clients will access it remotely through an interface
- you will sell the software together with the hardware and a proprietary operating system, which does not allow anyone to get the ones and zeros of your software
So, the only way to prevent GTA6 being "decompiled" and "forked" by AI models is to run it remotely (with a video interface), or sell it together with a proprietary console :D
[3 comments hidden]
not to mention there are alternative revenue sources anyways.
[hidden]
Most open source software is written by corporations which have a complimentary motive. Think hardware manufacturers writing drivers because it makes their products more saleable or Google writing Go because they needed a systems programming language.
[10 comments hidden]
I don't mean to discredit LLM capabilities, it's just that these examples are heavily favored by what's already documented online.
[hidden]
[4 comments hidden]
[2 comments hidden]
[2 comments hidden]
I don't see what's unique about GTA6. It's just larger in scope if you wanted to decompile or greenfield a custom engine.
But at the end of the day you'll be able to unpack the assets yourself and immediately have the worldmap running in a browser in Three.js. And once you're there, you can vibe-code any game you want on top of it.
[2 comments hidden]
[3 comments hidden]
[6 comments hidden]
> @kuckir, to be clear about the lineage: PhotoSuite started from the Photopea build mirrored at https://github.com/ruanjiyang/Photopea-Offline, and the README credits Photopea as the primary inspiration and prior art. Over the past year it's been rewritten and rearchitected module by module, retargeted for desktop, restructured into ~330 source files, with a lot of features Photopea doesn't have. It's a rewrite of that lineage.
That Photopea-Offline is an unofficial rip of the actual app. Pretty sure using a pirated version doesn't suddenly grant you license rights to use & extend the code into another competing product...
[hidden]
> That's a bold accusation. Would you care proving which bits of the code are "stolen"?
https://github.com/eolix/photosuite/issues/77#issuecomment-5...
to banning photopea, to when photopea responds with a 2nd account re: some duplicate code which is very hard to explain w/o being, well, duplicated to what you pasted above.
[hidden]
[4 comments hidden]
edit: it's not, the reddit post https://www.reddit.com/r/Bard/comments/1wxmqpt/ive_created_o...
and github repositories
https://github.com/storytold/photocraft (Photoshop)
https://github.com/storytold/vectorcraft (Illustrator)
https://github.com/storytold/filmcraft (Premiere)
https://github.com/storytold/lightcraft (Lightroom)
https://github.com/storytold/printcraft (Acrobat Pro)
https://github.com/storytold/effectcraft (After Effects)
https://github.com/storytold/designcraft (InDesign)
[hidden]
It's embarrassing to be honest. The eolix guy couldn't even respond to the very first piece of evidence by the Photopea creator, before spewing some clearly and poorly generated, LLM response. So of course he'd resort to issue-closing, title-changing, banning, bullying and then Whatabout-ism.
Beautiful rainbow of moral failures...
Goodluck with that "internal audit" buddy. The internet never forgets.
A side note: I wonder what pre-Microsoft Github would do in such cases. I don't think I've ever seen modern Github take action against any clone repo with legitimate copyright issues.
[hidden]
[hidden]
I don't like it but thats the situation on the ground IMO
IvanK_net[7 comments hidden]
Thank you all for your support! Many repositories like this one exist on GitHub, I tried to report in in the past, but I was completely ignored by Github / Microsoft. I feel pretty powerless here :( I tried to call them out publicly - https://x.com/photopeacom/status/2106877355738140875
This "PhotoSuite" thing got me a bit angry, since the author presented it as an original work, when I clearly see that such a project can be made from my "pp.js" file in two hours using Claude. Also, I believe that their README.md did not mention Photopea before I wrote my first comment there.
Thousands of people shared "PhotoSuite" on social media and nobody minded the fact that they don't know who the creator is. The creator is still offering it on their website as their original work: https://www.photosuite.app/
We live in interesting times. AI can (or will be able to) de-obfuscate every bit of code that was ever published, convert binaries to readable C++ and so on. So, in theory, AI models will train on the source code that we consider "closed-source" now, and will be able to recreate this software if asked. But it wouldn't be possible if a real person did not spend thousands of hours of their life to write that software years sooner.
I have always been excided to see people make AI create something new, what didn't exist before. But so far, I mostly saw only "approximations" of expensive software, when AI tries to recreate each feature and each button according to what it thinks it should do, or "forks", when AI takes the full code of something and tries to "bend" it to hide the similarity with the original work.
vdfs[4 comments hidden]
Genuine question: isn't this what photopea did to photoshop?
IvanK_net[2 comments hidden]
In this case, it was a clear copy-paste of my code, whith the variable names changed by the AI.
uurrnn[hidden]
I am still very attached to it though. For no good reason other than "it's mine", I think.
Isn't it a good thing software can't be closed? We have to use someone's tool though, and ego is inevitable, so idk? 100s of separate "open source" versions and people use what they think is the best?
Is it just about accountability? and having an author/human attached to the product to direct it? Choosing the person you have the most faith in?
/rambling
mrandish[hidden]
There's no evidence the PhotoPea author ever decompiled PhotoShop binaries. He emulated a desktop program's functions, menu structure and look in a web app by writing original code. Even if you had the PS source code, delivering a PhotoShop-like experience in a web page requires a lot of original work (especially in 2013). Before PhotoPea, Adobe had said that making PhotoShop browser-based would be extremely difficult, if not impossible and never be performant.
PhotoPea proved that with enough work and skill it was possible. Having an LLM coding agent look at PhotoPea itself and turn it into a copy of PhotoPea and then representing it as your own work is not at all the same.
tonyedgecombe[2 comments hidden]
This is the second time we have heard this complaint in the last week. Previously it was https://news.ycombinator.com/item?id=49832406
It feels like we need to be more and more vigilant about relying on tools from these big technology companies. Especially if you are running a small business. They really don't give a shit about you unless you have enough pull to get on the front page of HN.
IvanK_net[hidden]