|
|
|
|
|
by mercurial
4958 days ago
|
|
All these measurements should be considered in the same light: what is the projected TCO of the software? And this includes a number of metrics: - programmer productivity - hardware costs - speed - flexibility - ease of maintenance - barrier of entry - interop with other software How easy will it be to maintain the software in ten years? Wrt to Python, it's a fantastic language, but I've become scared of large codebases in dynamic languages. |
|
Fair enough. It seems to me that if an application has high performance demands and is expected to be in service for years, it should eventually be rewritten in a faster language. I find myself designing/developing programs in Python because development is so fast, then rewriting the result in a faster language after the design phase is over.
The rewriting phase is basically a translation, not a redesign. In most cases I know exactly how the program should behave, so there's no design taking place.