@whitequark @dalias @wwahammy plus, if you're worried about CI cpu-hours you could also Just Make Your Cold Build Faster. in C and C++ particularly there's a lot of approaches there with varying degrees of flakiness (e.g. unity files, pch, fixing your code structure), where the incremental build is only one flaky and often ineffective option of many.

@dalias @whitequark @wwahammy problem with trust in this context is that it's not sufficient to trust without some approach to detecting and remediating failures, and then when you have infrastructure for detecting and remediating incremental build failures it often looks a lot like just clearing the cache and running the whole build again. tension between "i should be able to rely on this working" and "it's not physically possible to be sure this always works, so i need to manage the fallout"

@erwinrossen @glyph generally speaking, but 'shader' tends to refer to programs that run in a graphics context, and 'kernel' tends to refer to to programs which run in a non-graphics context. historically shaders were all for... shading. and now they're mostly generic-ish computer programs. (also it's a bit ecosystem dependent "cuda kernel" is nvidia speak. dx12/vulkan calls everything "shader". amd hip uses "kernel". unity uses "compute shader assets" which are composed of "kernels", etc)

@wingo "i always thought gandalf is gay" - tolkein

fwiw i don't really know what that machine was responsible for, i'd guess mostly reverse-proxying backend apis?

@aras oh no corporate aras has escaped