There have always been Adobe alternatives and many are more than 50% functional.

> one-shotting complex software like this

You mean one shotting slop that barely works and lacks mature software stability with decades of fixes/features and improvements? No serious professional would ever use something like that. Like I’m the first to join the party if there is any hate to put on Adobe, but their closed source platform isn’t going anywhere. Only a paradigma shift could

We're one major LLM release away from being able to spit out _the whole adobe suit_ in a single prompt, while being safer, faster, and more featureful. I wonder at what point will tech companies stop interrogating candidates on useless Leetcode problems.

Here's my technically grounded response:

As far as I understand, inspecting the compiled binaries in any way would violate clean-room principles. At a minimum you'd need (A) one set of agents documenting the behavior of the executing binaries, e.g. manipulating the UI, and reviewing documentation and training manuals, and (B) a second set of agents whose only input is the output of the first set of agents. I'm not sure whether testing the real and AI generated agent side by side with equivalent inputs would constitute clean-room, although it might be legal.

I agree that a large part of the value of a product stems from "thousands of tiny design, engineering, and product decisions." But I don't agree with your conclusion. If the goal is to replicate the behavior of an existing piece of software then all you need to do is observe the behavior and replicate it. You don't need to engineer it in the same way, or arrive at it by making the same engineering and design decisions. Of-course in the end all you have is the replica, not the engineering and design heritage, product management, or the teams to carry the work forward. But that is the same problem open source "clones" of commercial products have often suffered from.

> But Photoshop is the product of thousands of tiny design, engineering, and product decisions. The idea that all of those decisions can simply be “decoded” from compiled binaries is laughable.

I actually think a couple passes with AI through the product will cover 80+ % of the use-cases people will have and people will have no problem switching to the new thing.

Based on how non-functional it is I would say Claude churning for a weekend or less.

This was the result of a _single_ prompt. Which actually shows the power of modern LLMs. I already have a from scratch C++ implementation of Photoshop, in my own custom UI toolkit, with my own custom GPU shaders. From scratch. Whole thing, ported over and I started last night. In preliminary benches it's roughly ~20-40% faster than their Photoshop rewrite. Will start heavy optimization passes and see how hard I can push it.