4 ms·

> Is "less code to maintain" really a valid concern? Do they actually have to maintain it after it's been written? Yes, it really is. And yes, you still have t

> Is "less code to maintain" really a valid concern? Do they actually have to maintain it after it's been written? Yes, it really is. And yes, you still have to maintain code that's been written. See discussion at https://github.com/golang/go/issues/25417 https://github.com/golang/go/issues/25417 The pure Go code was already faster than the assembly on some CPUs. For the other CPUs where the assembly was faster, we'd rather just fix the compiler to optimize better.

johnisgood 8y ago
> The pure Go code was already faster than the assembly on some CPUs. For the other CPUs where the assembly was faster, we'd rather just fix the compiler to optimize better. Yeah, it makes more sense to me than the reason (perhaps it was not intended to be the reason but I read it as such) provided on that page. Thanks for clearing it up.