|
|
|
|
|
by win311fwg
14 days ago
|
|
> 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 in allowing threads to run in any order. Of course, LLMs equally enable you to opt into reproducible output (temperature=0). Implementation details are immaterial. The human experience is always the same: Input one language, out comes another language. > So the really interesting bit to me is that this level of argument is even made. Yeah, it stems from a lack of base understanding of the technology. The "a compiler is deterministic but AI isn't" is always at the heart of the argument, but it isn't even true. 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 in order to learn more about it. Hey, that’s what discussion is for: to learn. |
|
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 in order to learn more about it.
Not splitting hairs is not the same as not knowing what a hair is.
> Hey, that’s what discussion is for: to learn.
You told me nothing I didn't know or didn't expect, because it gets brought up every time like clock work. It seems to be be part and parcel of not seeing or not wanting to see the woods for all the trees.