4 ms·
>But then you have no idea what the computer is actually doing. You trust it the same way you trust go compiler to do the right thing when you give it code to
by dominotw 11y ago
>But then you have no idea what the computer is actually doing.
You trust it the same way you trust go compiler to do the right thing when you give it code to compile.
- NateDad 11y agoThat's the nice thing about Go code... I almost always know exactly what it'll make the computer do. I know how much memory will get allocated, what the likely CPU usage is going to be, etc. The abstraction between the code and the computer is low, which helps lets a lot in understanding why your code is slow, or why it's producing a lot of garbage. "oh hey, here's a loop in a loop... oops, N^2 time".