The AI Disruption: Is "Software Over" as Brandon Thomas Claims?

In a bold declaration that has sent shockwaves through the developer community and Silicon Valley alike, software engineer Brandon Thomas recently took to Hacker News to proclaim that “Software is over.” Posting under the moniker “Echelon,” Thomas unveiled ArtCraft, a suite of open-source software clones that mirror the functionality of industry giants like Adobe Photoshop, Illustrator, InDesign, and even Microsoft Office staples like Word and Excel.

Thomas’s project was not built through years of grueling manual labor or massive engineering teams. Instead, he utilized the raw power of Claude Opus 5.5, an advanced AI coding assistant, to generate these applications in what he described as a “one-shot” effort—a single commit per application. This development represents a potential inflection point in the history of computer science, raising profound questions about the future of intellectual property, the economics of subscription-based software, and the sustainability of the “Big Tech” business model.

The Genesis of ArtCraft: A Vendetta Against Subscription Bloat

The catalyst for Thomas’s ambitious undertaking was surprisingly mundane: a frustrating interaction with Adobe’s subscription cancellation process. After being hit with a hefty cancellation fee, Thomas—like many consumers—found himself disillusioned with the increasingly aggressive monetization strategies employed by dominant software conglomerates.

Rather than simply switching to existing free alternatives like GIMP or Affinity, Thomas opted for a scorched-earth strategy: using AI to build functionally identical, free-to-use alternatives. While the core applications are free to download and utilize, Thomas has introduced an optional paid subscription model for users who wish to leverage integrated AI features within the ArtCraft suite.

The scope of his project is staggering. Within a remarkably short window, Thomas released clones for:

• Adobe Photoshop (Image editing)
• Adobe Illustrator (Vector graphics)
• Adobe InDesign (Desktop publishing)
• Adobe Acrobat (PDF management)
• Adobe Lightroom (Photo management)
• Adobe Premiere Pro (Video editing)
• Microsoft Word and Excel (Productivity)
• AutoCAD (Computer-aided design)

Chronology of a Digital Insurgency

• Early October 2026: Brandon Thomas posts on Hacker News, claiming to have successfully “one-shot” a Photoshop clone using Claude Opus 5.5.
• Mid-October 2026: The ArtCraft repository expands rapidly. Thomas releases a suite of clones for major productivity and creative software, all under an open-source license.
• Late October 2026: Tech media outlets begin testing the beta versions. While user reviews are mixed, noting bugs and missing high-end features, the functional similarity to proprietary software is noted as “impressive” and “disruptive.”
• Current State: The project remains in active development. Thomas continues to maintain the repository, while legal experts begin to debate the implications of using AI to reverse-engineer complex software ecosystems.

Technical Foundations: Rust vs. Legacy C++

One of the most fascinating aspects of the ArtCraft project is its technological underpinnings. While Adobe and Microsoft have relied on C++ for decades—a language that is powerful but notoriously complex and error-prone—Thomas wrote his ArtCraft suite in Rust.

Rust, a language prioritized for memory safety and performance, allows for modern, secure execution. By generating these apps from scratch using AI, Thomas has effectively sidestepped the “technical debt” that plagues legacy software. Because neither Thomas nor the AI he used had access to the proprietary source code of Adobe or Microsoft, the ArtCraft suite likely relies on reverse-engineering file formats rather than copying code.

From a technical standpoint, this is a masterclass in interoperability. By ensuring that ArtCraft can read and write the file formats of their counterparts, Thomas has lowered the barrier to entry for users who want to jump ship from expensive subscriptions.

The Legal Landscape: Copyright and the "Clean Room" Dilemma

The legal implications of ArtCraft are complex and largely uncharted territory. Traditionally, copyright law protects the specific expression of code, not the functionality of the software. According to the landmark Google v. Oracle ruling, using elements of an interface to ensure interoperability is generally permissible.

However, Adobe and Microsoft are unlikely to sit idly by. There are three primary legal avenues they might pursue:

1. Terms of Service (ToS) Violations

Both Adobe and Microsoft include explicit clauses in their End User License Agreements (EULAs) that prohibit reverse-engineering or analyzing the inputs and outputs of their software to recreate it. If Thomas utilized his own paid subscriptions to analyze how these programs interact with data, he may have violated these contractual agreements.

2. Trademark Infringement

While ArtCraft uses different names and logos, the visual design and workflow are intended to be "1-to-1" clones. Adobe could argue that this design mimicry is intended to create "market confusion," potentially tricking users into believing they are using official products.

3. Patent Litigation

Adobe and Microsoft hold thousands of patents covering specific algorithms and workflow processes. Even if the code is original, the way the software performs certain tasks might infringe on existing patents.

However, the "Clean Room" argument serves as Thomas’s primary shield. By using AI to generate code from a blank slate, he has arguably created a "clean room" implementation where the software is developed without any exposure to the original proprietary code, theoretically insulating him from copyright infringement claims.

The Practical Reality: A David vs. Goliath Scenario

While the legal theory favors the bold, the practical reality is bleak. Adobe is a company valued at over $90 billion. Even if Thomas is legally in the right, the cost of mounting a defense against a multinational corporation is astronomical. For a solo developer, the goal of Adobe or Microsoft wouldn’t necessarily be to win in court; it would be to make the cost of defending the project so high that Thomas is forced to abandon it.

Furthermore, as the project gains traction, the attention it receives may become its greatest vulnerability. Currently, Adobe is likely watching from the sidelines, waiting to see if ArtCraft becomes a genuine threat to their market share.

Implications: The End of Subscription Dominance?

The broader implications of the ArtCraft saga touch on a cultural shift within the software industry. There is a growing sentiment that large software providers have become extractive, locking users into "rental" models that prioritize shareholder returns over user utility.

The fact that even those who are staunchly anti-AI have expressed support for ArtCraft on forums like Reddit’s /r/antiai speaks volumes. In the eyes of many, the “evil” of AI-generated code is currently being eclipsed by the perceived “evil” of the subscription-based monopoly.

However, the "Ninety-ninety rule" looms large over the project. As the old engineering adage goes, the first 90 percent of code takes 90 percent of the time, and the remaining 10 percent takes the other 90 percent. ArtCraft is currently in that difficult second phase. While the core features work, the polish, stability, and edge-case handling required for professional-grade creative work are immense. Whether Thomas can bridge this gap—or whether the community will step in to help—remains to be seen.

Conclusion

Brandon Thomas has ignited a fire that may be impossible to extinguish. Even if Adobe succeeds in shutting down ArtCraft, the precedent has been set: AI has effectively lowered the barrier to entry for building complex, professional-grade software. The era of "one-shot" development may still be in its infancy, but the message to legacy software providers is clear: the monopoly on functionality is no longer absolute.

Whether ArtCraft becomes the catalyst for a more open, user-friendly software landscape or simply a footnote in the history of AI disruption, one thing is certain: the relationship between the software giant and the individual user has been permanently altered. We are entering an age where the power to create is no longer the exclusive province of the massive corporate entity, but a tool accessible to anyone with an AI assistant and a vision.