Re^3: No Hard Tabs in Code

in reply to Re^2: No Hard Tabs in Code
in thread No Hard Tabs in Code

8 spaces is a ridiculous waste of real estate, to me. It's far too much for a single layer of indentation, and I find it _harder and slower to read_.

On the other hand, if you mandate tabs, and tab stops are smaller than the most extreme person prefers them to be, you get the ultimate disaster of mixed tabs and spaces--which is yet another good reason to turn everything into spaces.

A 5-space first tab, for paragraph indentation, was the standard for fixed width text for a very long time until not all that long ago. How quickly we forget.

Comment on Re^3: No Hard Tabs in Code

Replies are listed 'Best First'.
Re^4: No Hard Tabs in Code by alexbio (Monk) on Jul 02, 2010 at 17:22 UTC
[...] In short, 8-char indents make things easier to read, and have the added benefit of warning you when you're nesting your functions too deep. [...] Taken from Linux documentation (Doc*/CodingStyle) Chapter 1. I think this explains very well the idea behind the 8-chars tabs "movement". There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3. (The second quotation was just for fun :D) Alex's Log - http://alexlog.co.cc	[reply]

Replies are listed 'Best First'.

Re^4: No Hard Tabs in Code
by alexbio (Monk) on Jul 02, 2010 at 17:22 UTC

[...] In short, 8-char indents make things easier to read, and have the added benefit of warning you when you're nesting your functions too deep. [...]

Taken from Linux documentation (Doc*/CodingStyle) Chapter 1.

I think this explains very well the idea behind the 8-chars tabs "movement".

There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3.

(The second quotation was just for fun :D)

Alex's Log - http://alexlog.co.cc

[reply]

In Section Meditations