| 27 Oct 2023 |
 pwychowaniec | Jonas Chevalier: axel 🦀 has volunteered for maintaining Naersk - do you know what are the next steps here to implement this? 😄 | 05:41:15 |
 Mic92 | adisbladis: https://github.com/numtide/build-go-cache | 06:34:56 |
 adisbladis | In reply to @joerg:thalheim.io
adisbladis: https://github.com/numtide/build-go-cache Right, so you get one massive cache for the whole project, not any incrementality? | 06:36:06 |
| Mic92 | Just for dependencies and not the source of the project. | 06:36:53 |
| Mic92 | One could potentially split this up, but I am not seeing the benefit vs. complexity in this. | 06:37:23 |
| adisbladis | I always tried to get a recursive thing going as my motivation was to maximise reuse | 06:37:53 |
| Mic92 | I have the feeling that the eval time of this would be higher than the speed of the go compiler. | 06:38:30 |
| adisbladis | But when I did that all compiler savings were dwarfed by copying files around | 06:38:38 |
| Mic92 | the cache also speeds up proxyVendor = true; | 06:39:26 |
