Originally posted by boxie
View Post
Yes, it probably won't matter if you are running a single crummy website on an off the shelf server, but if you are running a large scale operation, you certainly do not want to be 30 times worse than the optimal, because that directly translates to a 30x greater infrastructure cost, if not even higher.
But try and see the world beyond the tip of your nose. On a global scale, all web services would need 30x higher maintenance, and would have a 30x higher environmental footprint. In the end, all those costs apply to the end user, one way or another.
And lastly, high performance language do not necessarily need to be slower to develop in. Throwing extra money and hardware at inefficient code... that's what the money making industry likes, and that is also the reason the standards for code quality are abysmally low. But I am sure you never felt like software runs like a sloth or is needlessly bloated, right? Just like you never felt bad for being strong-armed into making additional purchases that could have been avoided. Yes, one does have to balance priorities, but in the end you do have to try to make the best of what you got, throwing money at problems is never a good solution.
Comment