|
|
|
|
|
|
by customguy
14 days ago
|
|
|
> 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 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. |
|
|
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.