Posted on 10/10/2026 10:09:58 AM PDT by srmanuel
A small team of 2-4 "Vibecoders" from a company called Aircraft, using Anthropics Claude AI Opus 5.5 model, fed the binary machine code for Adobe's Creative Suite of software products into Opus 5.5 and have produced a workable source code and the entire suite of products which they have released as open source. Acknowledging that plenty of bugs exist in the initial release, the company is saying within a month they should have all the bugs resolved.
The implications of this are HUGE, if 2-4 people using AI can feed the binary machine code of any proprietary into a current AI model and produce working source code and software, is any software safe from being reproduced.
Here are a couple of more links to the story.
https://medium.com/design-bootcamp/two-programmers-use-ai-to-clone-adobe-photoshop-now-nothing-is-safe-ed8675a8a2fb
https://arstechnica.com/ai/2026/10/software-is-over-bold-ai-developer-takes-aim-at-adobe-with-open-source-clones/
|
Click here: to donate by Credit Card Or here: to donate by PayPal Or by mail to: Free Republic, LLC - PO Box 9771 - Fresno, CA 93794 Thank you very much and God bless you. |
AI - Provide source code for this operating system, without the parts that spy on me.
The movie, “The Matrix”, missed the mark. Batteries works, probably, best for a movie, but in reality we will all be programmers.
The company that licenses proprietary software for auto repair just pooped its pants.
Good thing Trump is countering the antiquated AI with his new Superior Intelligence SI.
Now do John Deere firmware.
I will say having worked with private sector plus fed/state gov software applications it will only be a bigger challenge the older and more convoluted it is. Basically the more
function points the less likely it is all necessary and more likely some parts are non-functioning. SI will need to learn and re-learn garbage in, garbage out. The older the app the more likely it is crap in dire need of a complete re-write.
Reverse engineering the functionality is one thing, but ever since the days of Lotus vs, Paperback Software, copying “Look and Feel” has been an issue. I am not sure how that plays out versus free open source, but I am pretty sure that changes have to be made to avoid successful lawsuits from Adobe.
I hope that society does not fully go in the direction of socialism. I do not like forced redistribution of wealth from workers to non-workers.
That being said, it seems more and more obvious to me that the traditional economic model is becoming obsolete. People don’t want to work like dogs for little reward. People are finding ways to get what they need without the Big Corporations squeezing them for every last cent. If our culture decides to abandon conspicuous consumption, and if AI and automation continues to improve (which it certainly will) then we will have a whole lot of people who live just fine without needing to work 40 hrs a week for a major corporation.
They're right, no human being could steal code like that.
"“Now you can just create 1:1 functional equivalents, clean room, that are highly performant and cross-platform. Nothing is stopping you,” Thomas wrote. “We’ll replace Google Search, we’ll build our own smartphones, we’ll build better infra. We’ll remove all the ads and de-enshittify the entire tech world.”
Who appointed you the Guardian of the Galaxy? He'll look good in orange for theft of IP.
Perhaps you’re right, but think of the implications, 2-4 people working with an AI/SI model in a matter few days reverse engineers a widely sold proprietary software and releases it as open source.
Knockoff software will be like knockoff handbags.
The real thing will always be better.
It looks like theft to me. I’m sure there are many proprietary copyrighted “algorithms” that would have to be violated. They would have to have bought a real license to give it code, and that means they agreed to an extensive licensing agreement. Some tweaks to that would protect the IP probably.
But it is concerning. This stuff is crazy good. Old programs written for Dos brought up to Windows standards easily. Not hard, easily. This agentic stuff is powerful and crazy good. And cheap.
Yeah, Deere is gonna poop its pants, too.
American farm boys will be ALL OVER this.
In my limited experience of software development we never found all the bugs and fixed them nearly as fast as we did when we actually put the application to work.
Funny how that pans out.
Think of some of widely used enterprise software, Microsoft Office, Oracle, etc., now that someone has done this with Adobe Software, it’s opened the flood gates for everyone to now try the same thing with other software.
That’s been going on in some form or another since the 80s. The entire IBM Clone industry (which led to the PCs most of us are sitting in front of now) was born of people reverse engineer IBM’s BIOS.
Also, Adobe write crappy code and makes bad products, screw em.
The report overstates both the method and the immediacy. The ArtCraft (not "Aircraft") project used Claude Opus 5.5 for an AI-assisted clean-room reimplementation of Adobe’s Creative Suite in Rust, relying on public specifications and observed behavior rather than feeding proprietary binary machine code into the model. The resulting applications—PhotoCraft, FilmCraft, and the others—have been released as open source, but they remain early-alpha software with documented feature gaps, incomplete professional workflows, and the expected early bugs. ArtCraft has stated an ambitious timeline, initially aiming for near-full feature parity within a month and later qualifying that to months rather than years. That goal is unproven; current independent assessments and user reports still describe the tools as far from production-grade daily drivers.
Even if the team closes most functional gaps on that schedule, the broader shift is real. Capable coding agents dramatically lower the time and cost of producing workable functional equivalents of complex software. When platforms simultaneously move “headless”—exposing their capabilities through APIs, command-line interfaces, and protocols such as the Model Context Protocol so that AI agents can discover and invoke them without a proprietary graphical interface—the specific closed-source implementation loses durable value. Salesforce’s Headless 360 already treats its platform as composable infrastructure rather than a locked application that users must enter to operate.
What remains difficult to replicate will be the surrounding system: network effects, brand trust, reliable support, transparent quality signals, and deep integration into existing workflows. Established companies will be forced to adapt by opening more APIs and agent-accessible surfaces, competing on operational reliability, and ecosystem depth rather than code secrecy. Those that move early can convert the change into a distribution advantage. Those that resist risk accelerated commoditization and slower growth as agents and open alternatives erode the remaining barriers to functional substitution.
I've been using Claude Code on hobby software projects and the results are really astounding. I just ended usage of a Continuous Glucose Monitor. Like many CGMs, the sensor was unstable and performance, reliability, repeatability, and data quality were deteriorating. I used Claude to analyze the data stream, identify when deterioration started, when it accelerated, and develop metrics for performance problems. I was able to isolate the data in Days 2-7 as being high quality and reliable. I used the analysis to get Dexcom to send me a replacement sensor.
The future of AI will be dominated by legal disputes including but not limited to liability, plagiarism, and copyright infringement.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.