Developer Used Claude to Write Rust Alternatives to Four Adobe Programs

One programmer, the Rust language and the Claude AI model. According to CNews, that is what went into a set of free replacements for Photoshop, Premiere, Lightroom and InDesign. The code is published on GitHub, while posts linking to it are reportedly being deleted quickly. The article does not name the author or give the exact number of programs in the set: it refers to the four named products and "others" from Adobe's lineup.

What is actually known

There are few facts, and they should be separated from speculation.

• Author: one developer who worked alone.
• Language: all the code is written in Rust.
• AI: Claude helped with development; to what extent is not disclosed.
• Targets: a raster editor (Photoshop), video editing (Premiere), photo cataloging and processing (Lightroom), page layout (InDesign).
• Distribution: GitHub, free of charge.
• Link removal: posts are disappearing, but who is removing them and on what grounds has not been confirmed.

The source says nothing about licensing, functionality, format support or performance. There are no metrics to rely on yet, either.

Why the word "killer" is premature

Photoshop has been in development since 1990. Over that time it has accumulated PSD support, color management, dozens of filters, a plugin ecosystem and GPU acceleration. It is this tedious compatibility, not a set of basic brushes and layers, that keeps professionals on it. Writing a program that opens images and draws on them is quick work. Reproducing the behavior that studios and print shops depend on is much harder.

The choice of Rust looks sensible. It offers speed close to C++ and protection against a whole class of memory errors, which matters for editors that parse complex file formats. In this setup, Claude covers the volume: boilerplate code, interfaces, converters. The bottleneck stays the same: someone has to verify that the result works on real projects, not just in demos. One person with an AI assistant can produce a lot of code quickly. They cannot test it just as quickly.

Link removals: more theories than facts

CNews allows that Adobe itself is behind the removals. That is an assumption, not an established fact. Links could be disappearing because of a copyright or trademark complaint, because of names resembling Adobe brands, because of the possible use of proprietary specifications, or because of the platforms' own rules. Less dramatic causes are also possible: social network spam filters that react to the mass sharing of a single link. So far, nobody has shown either a complaint or a response from the company.

What to do if you want to try it

A story about a "free Photoshop" is a classic reason for caution: malicious builds are regularly distributed under such names. If the project turns up, you should not download ready-made binaries from random links. It is safer to build from source yourself, after checking that the repository belongs to the stated author and reading the license. Teams and studios should also weigh the legal risk: code of unclear origin that a rights holder may be disputing is best kept out of the workflow.

For anyone who needs an Adobe replacement right now, there are proven open-source options: Krita and GIMP for graphics, Darktable and RawTherapee for RAW photos, Kdenlive for video editing, and Scribus for page layout. The Rust project is worth bookmarking as a signal: one person with a language model is already taking on tasks that used to take whole teams. How well it turned out will remain an open question until the first independent tests.