>>17
That's because you assume only polar opposites.
With FORCED INDENTATION OF CODE you have no choice, there is only most readable code option.
With something like Perl you have the option to have your cake and eat it too.
You can optimize where it matters and have readable code where it matters. Or you can have all readable, and even then, you have options as to what is most readable to the programmer or programming team.
This, my friend, is freedom to optimize what works best for you.
What FORCED INDENTATION OF CODE tries to do is alleviate the issue of different design philosophies by applying a single standard at the expense of efficiency. And by efficiency I don't mean ALL CODE IN ONE LINE extreme. By efficiency I mean the balance between
readability and
ENTERPRISE OPTIMIZATION.
If you enjoy having purely readable code, that's cool bro. I don't care, but there's a problem when you go out and try to convert people to your new church.