ArtCraft's AI-written Rust clones copy Adobe's interfaces faster than one developer can audit them

The part that got cheap is the surface. Tom's Hardware says free Adobe alternatives often use different layouts and workflows, and that Affinity, the closest Photoshop rival, still has a learning curve and no integrated suite ^[13]. ArtCraft is aimed at that gap. Its developer set out to reproduce the familiar layouts and functions of each product ^[19]. For people whose workflows have been built on Adobe for decades ^[15], a matching layout cuts retraining.

Function is the harder half. Phoronix reports the apps debuted the week before its story and had already gone through multiple releases on fast AI iterations ^[6]. Commenters still questioned whether the apps work as claimed, and the project has features it has yet to replicate ^[12]. For a one-month parity target to matter to a working shop, the apps have to handle the files and steps those Adobe workflows already depend on.

Review is the part one person cannot scale. A single developer has generated potentially hundreds of thousands of lines across several programs, Tom's Hardware notes, with no team to verify them ^[9]. The concerns raised include privacy problems, malicious code and unsafe file handling ^[11]. The repositories stress repeatedly that the code is Rust ^[3]. In my view that choice does nothing about malicious code or privacy leaks.

The outlet also cites Sonar's 2026 State of Code survey, in which 96% of 1,100 professionals said they do not fully trust AI-generated code ^[10]. That works out to roughly 1,056 people, if every respondent answered the question ^[16]. The figure measures sentiment in someone else's sample. It would transfer to ArtCraft only if this code failed the way those developers fear, and neither report describes any outside review of it.

The design choice I would keep is the agent interface. Each app exposes its tools and menus to AI over a JSON control channel and an MCP server ^[8]. Anything an agent can drive, a test script can drive. The same channel could replay a scripted edit and compare the output against a reference file. I think it is the most practical way for one developer to check function parity across this much generated code.

Phoronix put both "clean room" and "open-source" in quotation marks ^[18], and described the project as relying predominantly on AI to produce the reimplementations ^[5]. The original Reddit post has since been removed ^[7]. Its author posts as u/ai_art_is_art ^[1], a handle picked with no visible interest in calming an Adobe forum.