I used to think like that: learn all of the quirks and the internals behind them, and you always have an explanation. With postgres, I always had an explanatio

I used to think like that: learn all of the quirks and the internals behind them, and you always have an explanation. With postgres, I always had an explanation why it was doing so much work on every update, and why replication was so hard, and why checksums were impossible to implement efficiently, and why index only scans wouldn't work, and... After seeing that all of these things were fixed by people who didn't think that way, I changed my mind. This Go behavior is surprising behavior and non-deterministic. Changing a constant can have some bizarre action at a distance that breaks your code. It affects ordinary code even if the author doesn't care about these details. I really don't see anything good about it even if you do understand it.