Earlier quoted context omitted.
> and the fact that you get wildly different output for the same input with LLM, not so for compilers. Quite so. It is true that most compilers allow you to opt in to reproducible output, but it is generally not the default [iirc, gc is the only mainstream compiler that makes always reproducible output a design requirement]. There are advantages to not have to worry about reproducible output, like performance gains i…
> gc is the only mainstream compiler that makes always reproducible output a design requirement This is just splitting hairs. And temperature = 0 is not comparable either, because the we will not keep models trained on data of a specific point in time around forever. > Implementation details are immaterial, but when you don't understand the implementation it stands to reason that one would want to focus on that facet…
Equally, if you replace one compiler with another, it is almost certain that the output will not remain stable, even when you have enabled reproducible builds. You are not going to find a difference on the outside, even if implementation may differ under the hood.
> You told me nothing I didn't know or didn't expect
What's in it for you, then? I have been able to learn about your character, which is quite fascinating. Technology is pretty boring, which is why nobody else was talking about a technology implementation to begin with, but HN accounts are quite interesting to learn about. Seems to me like a complete waste of time if you cannot learn anything from it.