5 ms·
1. Strict Enforcement of the Google Code Guidelines People who are undisciplined typically don't like discipline when they first encounter it. This doesn't res
by warent 9y ago
1. Strict Enforcement of the Google Code Guidelines
People who are undisciplined typically don't like discipline when they first encounter it. This doesn't restrict "Coding style" like the author suggests. Coding style and code format shouldn't be conflated.
2. Broken Package Management
It's not broken; it's intentionally limited. A "vendor" directory is natively supported by Go to account for this; use Glide or similar for more complex use-cases.
3. No Inheritance
It's a pattern of programming just like any other. In return you get first principles code and tiny lightning fast binaries.
4. Missing Generics
While I agree this isn't awesome, you can resolve this using Reflection.
5. Feature-Lacking HTTP Library
??? The author is missing the point of Go here entirely.
- chank 9y agoExcept go does have inheritance... basically: https://play.golang.org/p/yDejKzS4EQ https://play.golang.org/p/yDejKzS4EQ
- concede_pluto 9y agoGo binaries are small and don't do much initialization work but they don't run especially quickly, mostly due to GC and value->interface conversion and dynamic dispatch.
- warent 9y ago> and value->interface conversion and dynamic dispatch Thank you for the reply. Where can I learn more about that?