Wow. There are so many things wrong with this post that I almost want to consider it to be marked a troll. I'd say someone hacked your account to hurt your XP, but too much energy seems to be put into the post for that. I appreciate that you feel "righteous" but I think your energy is misplaced on this one.
I'll start out this diatribe by stating... this is the most blatant flaw in the PBP.
That's almost worth a "--" right there. PBP has a lot of great recommendations, but of the blatantly bad ones, tabs vs spaces can't possibly beat recommending half-a-dozen or so brand new CPAN modules and declaring them "best practice". (With Class::Std being my personal least-favorite among them.)
tabs as code-metadata
Metadata should derive from the data -- it shouldn't drive the data. declaring "tabs are better" so that people can search code by indentation level is one of the most bizarre justifications I've ever heard. Code-search should be one of the last considerations for code formatting choices.
For me -- it comes down to simplicity. Too many things need to go right for tabs to work properly the way you describe. You have to have a smart editor. You have to only use tabs to your indentation level and then you have to use spaces for any alignment after that. That's too easy to get wrong. (Plus you have to think about it.) And everyone you share code with has to get it right as well.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
In reply to Re: Tabs vs Spaces lets give this a go
by xdg
in thread Tabs vs Spaces lets give this a go
by EvanCarroll
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |