Agree with all points. Additionally, compilers are also incredibly well specified via ISO standards etc, and have multiple open source codebases available, eg GCC which is available in multiple builds and implementations for different versions of C and C++, and DQNEO/cc.go.
So there are many fully-functional and complete sources that Claude Cowork would have pulled routines and code from.
The vibe coded compiler is likely unmaintainable, so it can’t br updated when the spec changes even assuming it did work and was real. So you’d have to redo the entire thing. It’s silly.
Agree with all points. Additionally, compilers are also incredibly well specified via ISO standards etc, and have multiple open source codebases available, eg GCC which is available in multiple builds and implementations for different versions of C and C++, and DQNEO/cc.go.
So there are many fully-functional and complete sources that Claude Cowork would have pulled routines and code from.
The vibe coded compiler is likely unmaintainable, so it can’t br updated when the spec changes even assuming it did work and was real. So you’d have to redo the entire thing. It’s silly.
Nah bro. Just tell the agent to be a super duper distinguished software developer and write no bugs and keep the code maintainable /s
Updates? You just vibecode a new compiler that follows the new spec
“I want to add a command line option that auto generates helloworld.exe”
“That’ll be $21,000.”
Ah, that’s the problem, we’ve been getting all these chatbots to generate “hellworld.exe”.