>>... it's the person who writes the code that makes that judgement. No one else.
>
>If one is writing the code for himself, others will have no say about his coding convention. However if the code is written for others, particularly the customers who buy the product, the programmer is responsible for eliminating foreseeable crashes.
>

Ben,

To support your POV, you clipped out much of what I said. Here's the complete post

"The one, and only reason, to use such conventions is to make the code more readable. From my POV, regardless of whatever minor performance improvements occur, it's the person who writes the code that makes that judgement. No one else."

The only reason that conventions exist in the first place is to make the code more readable for those who have to maintain it, not the people who buy the product.

If performance is an issue, then it must be addressed from the architecture and design in the first place. Writing code considering performance above readability is a serious mistake from the start. There is "performance" and the "appearance of performance".

In short, programming to save a few milliseconds here and there is a very bad practice.