4 ms·
It isn't just performance that you can throw more instances at perhaps. It is also about dev productivity, readability of code (in spite of writing clean code),
by silentsea90 5y ago
It isn't just performance that you can throw more instances at perhaps. It is also about dev productivity, readability of code (in spite of writing clean code), not making silly errors that would be caught by static typing easily.
Building in Python feels like playing Jenga - easy enough at first but every change after a while is made with a silent prayer and anxiety.
- spenczar5 5y agoRight, that is much more important than performance, as I said as well. But I think that whether your Python will age well or your Go depends more on the team and their level of experience with either tool. Use something reasonable, and pretty familiar, and stick to it. Don’t do dumb stuff like going crazy with metaprogramming, and avoid excessive abstraction - but those are just always the required conditions for keeping your group functioning well. Any language can be abused; abstraction is not really a property of a programming language choice.