> No, this all started because you asserted that compilers are equivalent to AI.

I asserted that typing in what you want and feeding it into something that outputs code is that something being a compiler. Call that AI if you want, but I've always known that to be a compiler. Again, I'm old, so maybe terms are changing and I'm not in touch with that. I don't know. I'm not sure I care. Logically, "compiler" when used in my writings means what I intend it to mean. It makes no difference what others think it means.

Compilers are not equivalent to AI as, at least in my day, AI is a field of computer science, not any specific type of tool. But compilers are typically designed as rule-based “expert systems”, which traditionally has fallen under the AI umbrella. Well, unless you are in the "its only AI if I don't understand it" camp. In which case nothing is AI in any meaningful sense.

Not that it matters as "compiler" always used to refer to the functionality, not how it is implemented. If you built a C compiler that used neural nets, it would still be a compiler. If you built a C compiler based on mechanical turk it would still be a compiler. We call(ed) it a compiler because of what it does, not how it works beneath the sheets.

> There are multiple issues with this comment that I have outlined in my other comments.

It seems you found multiple issues based on the false premise of "typing in what you want" referring to natural language, but I wasn't talking about natural language. I was talking about programming languages. That is what you do with programming languages: You type in what you want, pass it to a compiler, and it generates code.