3 ms·
Yeah maybe. But I've found cache problems have always ended up costing more time than the cache ever saves.
by lmm 4y ago
Yeah maybe. But I've found cache problems have always ended up costing more time than the cache ever saves.
- wiseowise 4y agoYeah, you haven’t worked on projects big enough.
- lmm 4y agoI worked on what was claimed to be the second-biggest scala codebase in the world - 10MLOC, 500 contributors. Of course just switching off caching with 0 other workflow changes doesn't work, but I remain convinced that transparent caching does more harm than good.