Comment Re:You sure about that? (Score 1) 124
Your problem is that "I lack the capacity to imagine such a system" is not the same as "such a system cannot exist".
Good day.
Your problem is that "I lack the capacity to imagine such a system" is not the same as "such a system cannot exist".
Good day.
unless you train your own model that you know has never seen the source, an endeavor that costs 10s of millions of dollars.
Look up "StarCoder" because it does not require anywhere close to what you claim it does to train from scratch.
Don't buy the food, don't eat the food.
Are you ignorant or are you willfully ignorant?
Food has literally been engineered to be addictive. Don't believe the scientists? How about about looking at the food industry is responding by developing GLP-1 resistant food formulations. Given that obesity in the US has tripled in the last 50 years, if you don't suspect something odd is happening then you aren't looking.
Look at the facts, instead of trusting your "gut instinct" which you "know" is right because it's not.
You not only need to do a clean-room, you need to be able to prove it and that set-up does not allow it.
Actually, this setup would be more provable than having two people do it because you can literally record the entire process from start to finish.
Have two different computers with no hardware in common.
Computer 1 interprets the program and generates the documentation, saving it to a USB drive.
You unplug the USB drive and move it over to Computer 2.
Computer 2 reads the documentation and generates a new code base.
You can read the documentation and there was no other means of communication.
If you don't think a repeatable process is sufficient "proof" then you aren't being realistic and that's a problem with you, not the law.
Bonus points for selling all the unsellable Cybertruck stock to SpaceX
I was unsure about this specific claim but it appears to be accurate: https://electrek.co/2025/10/13...
While true, legally it makes no difference whether you steal the sources or the binary. It is still stolen.
Why would you steal it if you can simply license it?
And a clean-room implementation requires the code-writers to never have seen the original in any form. You cannot have an engineer analyze the original and then write a copy.
As the article explains, it's a clean room implementation because you use two different instances of an AI.
* AI 1 documents how the code works in a human readable descriptions. (i.e. does the reverse engineering)
* AI 2 constructs an entirely new codebase from the human readable descriptions in the documentation. (i.e. does the forward engineering)
Since AI 2 has never seen or analyzed the original code/binary and has only ever read the documentation about it, it is a clean room implementation.
Hence it is immediately plausible that having an AI train on the original or ingest it in a query and then writing a new version
The AI isn't training on the original (a very important point), it's generating written documentation on how it functions. The important part of this process is that it is creating a human level description and not simply an algebraic representation using words. Creating algebraic representation using words would simply result in generating a near identical source code which would be copyright infringement.
I do agree on the slop.
The current situation may or may not last but it's reasonable to assume that they are working on the problem of generating cleaner and more concise/less verbose code.
Despite the open source spin, source code is not required to do this as source code can also be generated from binaries. It shouldn't be shocking by now to learn that you can fully automate breaking down executable into functional source code with the addition of AI to "make sense" of the generated code. As such, this means that even large sophisticated and complex programs are also targets.
The real question is, who wants to deal with a massive amount of AI slop code?
This technology has been around for decades. I know because my boss is definitely one of these brainless clones.
The github page that's being pointed to has already taken down the code. Unlike the fools that posted the WinAmp source code, they actually know how to wipe out the commits. However, I found that searching github with leaked Claude Code language:TypeScript was enough to find several mirrors of the code.
I was so proud of this robot that I went up and gave it a hug. Everyone around me started yelling at me to get away and then the robot tried to install a solar panel on me. Long story short, I ended up in the hospital with a restraining order against to stay away from the robot.
THIS ROBOT IS NOT FRIENDLY.
You probably can't see how because of the same vision problem that prevented you from reading my post.
"simulate materials without ever having to construct them."
Finally, we're seeing applications of QC that are actually useful. I look forward to this expanding so that we can greatly advance materials science by being able to simulate materials without ever having to construct them.
I never cheated an honest man, only rascals. They wanted something for nothing. I gave them nothing for something. -- Joseph "Yellow Kid" Weil