Yes! I support this.<p>Readability should be prioritized across the organization or it will punish you later.<p>As a reminder, read about Kernighan's law:
“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”<p>Go is already a high-performance language, I am fine with people trying to squeeze out all the juice, until you have to trade-off readability.
From the article:<p><pre><code> Junior dev: My code is simple and easy to understand.
Mid-level dev: My code is subtle, clever, innovative, expressive, hyper-optimized, and ingenious.
Senior dev: My code is simple and easy to understand.
</code></pre>
<a href="https://twitter.com/bitfield/status/1219174978748370945" rel="nofollow">https://twitter.com/bitfield/status/1219174978748370945</a>
These seem to be arguments against using Go at all:<p><i>Performance doesn't matter</i>, so why use a compiled language, surely easier and clearer in Ruby, Python, ...<p><i>Go is fast</i>, my Go chums tell me a 1/3 of the speed of C/C++/Rust, plus GC stuttering, so if performance matters, use the latter<p>It seems that Go has a quite small window of applicability.