Top stupidest programming polemics

1. Gotos considered evil
For too long, schools have been successfully spreading the fallacy that gotos should never be used. Whenever I write code for someone and I use a goto, someone always complain:
"Man, you used gotos to [Handle errors/Break out of multiple loops/we]"
So knowing usually the kind of people I'm dealing with I respond:
"Why?"
But people always fail to know the real reason gotos used to be bashed on:
"They're just evil..."

2. Tabs vs. Spaces for indentation
Everyone using a real text editor knows that tabs are by far superior to spaces. There are easily at least five times more reasons to use tabs than to use spaces. Even worse than that, the reason I hear the most often to use spaces is that "tabs don't have the same number of spaces in text editors" while IT IS THE WHOLE FUCKING IDEA OF USING TABS, ANYONE CAN SEE AS MANY SPACES AS THEY WANT.


3. Global variables are bad

No. Just like gotos, they are when idiots don't know when to use them.

>>1
Everyone using a real text editor knows that tabs are by far superior to spaces. There are easily at least five times more reasons to use tabs than to use spaces. Even worse than that, the reason I hear the most often to use spaces is that "tabs don't have the same number of spaces in text editors" while IT IS THE WHOLE FUCKING IDEA OF USING TABS, ANYONE CAN SEE AS MANY SPACES AS THEY WANT.
B-but but but what about people who refuse to use any editor written in the last forty years and thus lack the ability to adjust the width of tabs?

Notepad lacks the ability to adjust the width of tabs, so does word, and so does shiichan

>>1
Goto breaks structured programming. Proper structured programming requires that you break out of loops using flag variables.

>>3
They chose to make their bed, now they have to lie in it.

>>5
Same with the kikes

>>6
And the ragheads

/prog/oyim A likes 8-space tabs.

void f(int x):
        printf("this is a formated string",
               this_is_a_long_statement,
               this_is_another_long_statement);
}

/prog/oyim B likes 4-space tabs.

void f(int x):
    printf("this is a formated string",
       this_is_a_long_statement,
       this_is_another_long_statement);
}

/prog/oyim B fixes /prog/oyim A's formatting ``errors.''

void f(int x):
    printf("this is a formated string",
           this_is_a_long_statement,
           this_is_another_long_statement);
}

/prog/oyim A see's the following:

void f(int x):
        printf("this is a formated string",
                   this_is_a_long_statement,
                   this_is_another_long_statement);
}

OP confirmed for mental goy.

>>8
If only /prog/oyim A and B understood that you cannot use tabs to adjust the position multiline function parameters since the spacing of tabs are known to depend on the editor. The other logical away of dealing with this problem (the one I prefer) is to simply leave a tab, regardless of where it is positionned after, since the indentation only implies that you're still writing the function call parameters.

+ being tabs and . being space:

void f(int x):
+   printf("this is a formated string",
+   .......this_is_a_long_statement,
+   .......this_is_another_long_statement);
}

tabs are superior to spaces...and long as you mix tabs and spaces together
Oy, vey! G-d forgive these goyim.

Besides, linebreaks and indentation are for goys who can't into parsing infinitely long single lines in their head due to inferior goyish IQ that cannot wrap their heads around infinity.

void f(int x):
        printf("this is a formated string",
               this_is_a_long_statement,
               this_is_another_long_statement);
}

Neither of those two are statements.