I assume you're some sort of programmer and I genuinely wonder how in the world can someone in good faith downplay non-determinism and ambiguity when talking about a programming language.
replyHigh-level languages can certainly yield inefficient code when compiled, or maybe different code among different compilers, but they're always meant to allow their users to know exactly what to expect from what they put together in their programs. I've always considered this a hard fact, I simply cannot wrap my head around working in a way that forces me to abandon this basic assumption.
So by your logic all the PMs, managers and customers are programmers, right? After all, there’s a human compiler that takes their input and produces a program?
replyThey are programmers when they write a prompt and get runnable code as a result, yes… but no if asking a human to write the code because if you have an intermediate, manual step between the text and the running code, you don’t have an automated process and hence it’s no longer even an application, let alone a “compiler”.
replyThe main difference is that the input to an LLM is in an ambiguous language.
replyA programming language is allowed to be ambiguous, I don’t know of a definition that excludes that!
replyAll programming languages I know of provide at least some guarantees about the program’s behavior.
replyThe language specs may be, but an implementation is never ambiguous. When you encounter and undefined behavior in the specs, that’s when you look at your compiler/interpreter docs.
replySo is JavaScript haha.
reply> That’s funny because it’s exactly, literally the same. The difference is it’s not deterministic.
replySo it is not, by your own admission, "exactly, literally the same".
Take it gently, the poor thing doesn't understand the difference between code and talking about code.
reply