With regards to this specific project, I think the best case scenario would be a bunch of developers taking the code and using it as a starting point, going through it with a fine-toothed comb and re-writing however much needs to be re-written. There’s never been a viable competitor to Adobe’s suite, and if this results in that, then we can at least applaud the outcome if not the methodology.
I haven’t tried the vibe coded suite, so I can only speak from what I’ve read, but my understanding is that it’s attempting feature and control parity with Adobe’s suite, which none of the other options have or try to have. If someone who’s used to Adobe can make the switch without having to functionally learn new software, it’ll be a lot easier to get people to actually do it.
With regards to this specific project, I think the best case scenario would be a bunch of developers taking the code and using it as a starting point, going through it with a fine-toothed comb and re-writing however much needs to be re-written. There’s never been a viable competitor to Adobe’s suite, and if this results in that, then we can at least applaud the outcome if not the methodology.
that would be 100% then, as its clearly impossible to be a clean room development.
Sure, and if the momentum and publicity this has generated is the catalyst that gets people to do it, then great. Good outcome in the end.
Why not just continue development and support for the projects already existing (krita, GIMP, PhotoPea, …)?
I haven’t tried the vibe coded suite, so I can only speak from what I’ve read, but my understanding is that it’s attempting feature and control parity with Adobe’s suite, which none of the other options have or try to have. If someone who’s used to Adobe can make the switch without having to functionally learn new software, it’ll be a lot easier to get people to actually do it.