Not a fan of it, but I have some experience behind why this happens!
Download gets corrupted (randomly) at some point. Corrupted file gets stuffed into the cache. Now, since everyone is using the cache, everything/everyone is broken because the cache is ‘always good’, and the key didn’t change!
So then, someone figured it out and turned off caching - and it fixed it.
And of course everyone has time to setup a reproducible test case for this random data corruption bug, and can wait for the language tooling to get fixing while all their builds break….
Or they just turn off caching and forget about it.
Download gets corrupted (randomly) at some point. Corrupted file gets stuffed into the cache. Now, since everyone is using the cache, everything/everyone is broken because the cache is ‘always good’, and the key didn’t change!
So then, someone figured it out and turned off caching - and it fixed it.
So now caching is always off.