Most projects I've been working on adopted spaces instead of tabs for their code convention. I personally hate using spaces though.
Same thing with putting the opening brackets for blocks in a new line instead of the same line.
Because I can indent everything how the fuck I want, so fuck you.
Also, you know how fucking annoying it is when I press back space once and it eats 4 spaces?
Fucking Tabfags I swear.
>Because I can indent everything how the fuck I want
With tabs you can (just set the tab width in your text editor).
With spaces you can't when you're working together - then you have to all agree on how many spaces to use.
>how fucking annoying it is when I press back space once and it eats 4 spaces?
You rather press backspace 4 times to unindend a line?
Indentation should be consistent, so you should never add/remove a single space.
I think it boils down to code monkeys being retarded and mixing up tabs and spaces.
Then it becomes easier to just ban tabs altogether.
But in a perfect world where everybody actually follows code conventions I don't see any advantage of spaces over tabs.
the only time this becomes a serious issue is in languages with significant whitespace where indentation acts as a block delimiter. such languages are a blight upon programming and must be eradicated.
>Single character for multiple spaces = smaller filesize
>Editors can change apparent indent easily
>Cool hackers use them
>Many retarded characters = bloat
>Increasing or decreasing indent becomes less trivial
>Code monkeys use them
"As a simple, self-contained example, consider the representation of program structure. Some observers objected to Go's C-like block structure with braces, preferring the use of spaces for indentation, in the style of Python or Haskell. However, we have had extensive experience tracking down build and test failures caused by cross-language builds where a Python snippet embedded in another language, for instance through a SWIG invocation, is subtly and invisibly broken by a change in the indentation of the surrounding code. Our position is therefore that, although spaces for indentation is nice for small programs, it doesn't scale well, and the bigger and more heterogeneous the code base, the more trouble it can cause. It is better to forgo convenience for safety and dependability, so Go has brace-bounded blocks."
Google literally says whitespace is cancerous. Why are you defending whitespace as syntax?
void main(argc, argv)
TAB_printf("This function is %s to be in %s %d %s.\n",
TAB_ "way too long",
TAB_ "programs which are trying to be under",
TAB_ "characters per line"
Tabs for indenting, spaces for formatting.
If you do space, you have to decide on an amount of spaces to use.
Do you use 3? 4? 8? 2? Everyone has their own preference, just like text editors, linux distros, and desktop environments.
So with tabs, everyone can set them to whatever they want, and they'll all see the text in their preferred tab width.
The same is possible with spaces in more advanced editors but is generally hacky and obviously will preclude less advanced editors.
All my (Pascalesque) style guides said and say 4 spaces are a tab. I also haven't seen anyone doing something else for a long time. Came in like heresy when I found out there are IDEs that translate a tab to another amount of spaces.
What? Every text editor I've ever seen literally just inputs four spaces with tab. Pressing tab then pressing backspace leaves you with three spaces. Does the difference happen only on Linux or something?