Great piece. I was thinking: "what programmers can do?" And came up with the "use compiled languages" answer. I compare Ruby and Haskell, as that's what I have experience with; but I expect it to hold true for any Ruby/Python/Java/etc vs C/C++/Haskell/Go/Rust/etc shootout. Just some typical numbers: Disk space to house one app deployment: 800MB Ruby/Rails vs 80MB Haskell/Yesod. Memory consumption of one instance: 350…
800MB Ruby/Rails What, really? How much of that is the app source? As a byte-shaving embedded developer I have zero experience with Rails. On the other hand, unless you're scaling really big, the CO2 cost of the computers is probably dwarfed by the cost of the developers commuting to work.
Little. Most is libs.
> [...] unless you're scaling really big, the CO2 cost of the computers is probably dwarfed by the cost of the developers commuting to work.
Yups. That's why I mentioned "scale". Personally I cycle 7 mins to work :)