3 ms·

>Go cares about scalability in the large Which features precisely have led you to believe this? I can't see any indication of that anywhere. You seem to be c

by copergi 12y ago

>Go cares about scalability in the large Which features precisely have led you to believe this? I can't see any indication of that anywhere. You seem to be creating a false dichotomy: "caring about abstractions and caring about scalability are opposing goals", so that you can ascribe one side of a nonexistent spectrum to go. >But if you're not on a large problem, that 10% of repetition will chafe you... Except that is simply not the case. The larger the problem, the more that duplicate code causes problems.

AnimalMuppet 12y ago
What led me to believe this is Pike's article about the design goals of Go. I don't know enough about Go to know how well it succeeds, but I know what the intent was.
- copergi 12y ago
  But you are falsely implying that the intent "be good for big projects" is opposed to the concept of "having useful abstractions". It is not. Go fails at being useful for big projects precisely because it fails to have basic useful abstractions. Those are most important in large projects. In a 1000 line program it doesn't matter much if I am repeating code, there's just not that much code anyways. In a 1000000 line project, it is a serious maintenance problem.