> when the C programmer has written the first working version, the FP programmer has tried 5 different solutions. ... none of which are necessarily faster than

> when the C programmer has written the first working version, the FP programmer has tried 5 different solutions. ... none of which are necessarily faster than the other 4 solutions. It's not just the architecture of your code that influences performance, it's also – sometimes even more so – the underlying details of your implementation, like arrays vs. pointer-based data structures; Athas' comment describes this pretty well. As a consequence, this statement: > it is always a property of the architecture or system, not of the programming language is wrong, simply because your programming language will heavily influence a lot of your productivity vs. performance tradeoffs.