>writes assembly to output bytecode
Ok
>writes C/C++ that outputs assembly
Ok
>writes Python that outputs C/C++ calls
Ok
>writes English that outputs Python
NOOOOOOOOOOOO NOT LIKE THIS!!!!!

natural languages are just a terrible way to "talk" to a computer, and in fact they are awful for any sort of formal specification period
even fantasy/sci-fi media have explored the topic of linguistic ambiguity to the death, it really doesn't take a genius to put two and two together
also an llm is not a compiler and python sucks

>>106035885
>are just a terrible way
If it's bad, why there's so many people crying about it?
>an llm is not a compiler
Not yet

>>106035659 (OP)
>english to python
this step is non-deterministic based on several factors like context, model, sampling params, etc. which is an enemy to doing good

>>106035659 (OP)
>>writes Python that outputs C/C++ calls
this is where the NOOOOOO should start

>>106035659 (OP)
The difference is your first three example will always output the same bytecode/assembly everytime and will do precisely what you wrote in your programming language of choice. LLM will output whatever the fuck it feels like and that may or may not do what you intended.

>>106036196
>If it's bad, why there's so many people crying about it?
if you want to get some specific result from LLM good luck.
t. mostly vibe coder

>>106035659 (OP)
>>writes assembly to output bytecode
>Ok
>>writes C/C++ that outputs assembly
>Ok
>>writes Python that outputs C/C++ calls
>Ok
All of these know what the code is doing.
>>writes English that outputs Python
>NOOOOOOOOOOOO NOT LIKE THIS!!!!!
This one doesn't and will probably drop your databases.

>>106035885