Did Claude write the compiler or interpreter? Those can choose what instructions get run, regardless of your source code.
There’s an old computer science discussion about trust and compilers. If I give you a compiler you can’t trust that it won’t insert a backdoor when you compile. So… You compile your own compiler from source… But that compiler puts a backdooring code into your compiler… What can you trust?
There’s an old computer science discussion about trust and compilers. If I give you a compiler you can’t trust that it won’t insert a backdoor when you compile. So… You compile your own compiler from source… But that compiler puts a backdooring code into your compiler… What can you trust?
burn it all down and go back to using abacuses and fingers! lol
Did you write it or did Claude write it?
farted out in 19 commits, over 3 days using copilot… scraped thoughtlessly with love <3
Did Claude write the compiler or interpreter? Those can choose what instructions get run, regardless of your source code.
There’s an old computer science discussion about trust and compilers. If I give you a compiler you can’t trust that it won’t insert a backdoor when you compile. So… You compile your own compiler from source… But that compiler puts a backdooring code into your compiler… What can you trust?
Well, we use CPUs that are not open source (I don’t yet, at least)
burn it all down and go back to using abacuses and fingers! lol
You can bootstrap your compiler toolchain from known good sources, or even from scratch (bootstrap C via Forth via assembly or machine code).