3 ms·
Well, let's play that game. 0.22€/kWh. So a 1kW server costs almost €2000/year. If you write Python vs. Go, the performance increase can be 10 fold, so you'd sa
by tgv 4y ago
Well, let's play that game. 0.22€/kWh. So a 1kW server costs almost €2000/year. If you write Python vs. Go, the performance increase can be 10 fold, so you'd save €1800/yr. So when you're running 55 Python servers, you could earn 1 dev by rewriting (assuming €100k/yr, all in).
Not to upset anyone: there are a lot of assumptions. It's just ballpark numbers. There's a large difference between Python v. Go for tensorflow and as a Django backend.
- michaelmior 4y agoSwitching languages is highly impractical for most teams. It is possible in some scenarios code written by an experienced Go developer is 10x faster than code written by an experienced Python developer. However, I think it's unlikely that a team writing Python is going to be able to write Go code which is as efficient as an expert Go developer. Even if they could, I think the productivity (in terms of being able to quickly implement features) of writing Python is significantly higher than Go. If only for the massive amounts of existing packages available, not including the language itself. I don't think this loss would be made up by a single additional developer. I'm certainly not saying that's not possible to have a highly productive team of Go developers. But I think expecting a team of Python developers to become Go experts is not likely to work well. (Dropbox potentially being a notable exception, although I don't know how they navigated this change organizationally.)