4 ms·
I strongly disagree with this view for applications, and mildly disagree for infrastructure projects. There is one thing I believe Go is by far and away the le
by bashtoni 3y ago
I strongly disagree with this view for applications, and mildly disagree for infrastructure projects.
There is one thing I believe Go is by far and away the leader at: keeping codebases maintainable over time.
Go is designed very clearly with this goal and it's excellent at it. The verbosity you complain about makes it much, much clearer what something is doing.
That coupled with some of the baked in opinions means it is significantly more straightforward to pick up code that you or someone else wrote a few years ago and modify it.
- steno132 3y agoSee, this is a problem I see many junior engineers struggle with: Excessive desire to make one's own life easier at the cost of customers. Yes, your codebase is nice and elegant and maintainable. But you haven't shipped as many features as the Python or Java developer, haven't delivered as much value to customers. Ultimately, the users suffer. It's a form of selfishness.
- JyB 3y agoI've never seen teams as efficient at shipping stuff as when they switched to Go. At multiple companies. Complete fallacy on your part.
- bashtoni 3y agoTo follow your logic: if I pump out a lot of features but others find my code difficult to maintain I'm not being selfish. If I write code more slowly that others find easier to maintain, that is selfish?
- mplewis 3y agoI’ve observed the exact opposite. Python teams are much slower to ship features than Go teams once the codebase grows to a nontrivial size.
- athreyac8 3y agoNever saw a Java developer ship things fast.