3 ms·
There's some truth to this. As a C# developer, I get to deal with a lot more: - Bikeshedding over LINQ - Going back and optimizing LINQ - Helping Developers
by to11mtm 5y ago
There's some truth to this.
As a C# developer, I get to deal with a lot more:
- Bikeshedding over LINQ
- Going back and optimizing LINQ
- Helping Developers understand someone else's LINQ, Reflection/Attribute Abuse
- Helping developers understand new syntax in each version of the language.
A large part of Go's philosophy is to more or less take away all of those tools from the Developer and try to force a style of code that is somewhat monotonous, verbose (in a way very different from Java), yet 'readable' by a developer with minimal experience.
- kaba0 5y agoAssembly is just as readable/simple, in that every single line is easy to comprehend. Yet good luck getting the big picture of an assembly program. The same is more or less true of Go. Abstractions can be bad, but in the majority of cases it is the only tool we have against complexity, and a method with an annotation may be thousands time more readable/understandable than the reimplementation of a given identical functionality for the thousands time.