GOTO is the only thing that makes sense. It's the "high-level" concepts like for-loops, functions and list comprehension that ruined programming.
series.append(series[k-1]+series[k-2]) for k in range(2,5)]
RAVINGS DREAMT UP BY THE UTTERLY DERANGED
I started coding with TurboBasic, which included the helpful innovation of GOTO {label} instead of GOTO {line number}, which allowed you to have marginally-better-looking code like:
GOTO bob
...
bob:
{do some useless shit}
return
which meant you essentially had actual, normal methods and you didn't have to put line numbers in front of everything. The problem was that labels (like variables) could be as long as you wanted them to be, but the compiler only looked at the first two letters. Great fun debugging that sort of nonsense.
WHAT DO YOU MEAN IT ONLY LOOKS AT THE FIRST TWO LETTERS WHAT
if goto make sense why don't you go to get some bitches
Because "get some bitches" is an invalid instruction
GOTO
GOTO is the only thing that makes sense. It's the "high-level" concepts like for-loops, functions and list comprehension that ruined programming.
RAVINGS DREAMT UP BY THE UTTERLY DERANGED
I started coding with TurboBasic, which included the helpful innovation of GOTO {label} instead of GOTO {line number}, which allowed you to have marginally-better-looking code like:
which meant you essentially had actual, normal methods and you didn't have to put line numbers in front of everything. The problem was that labels (like variables) could be as long as you wanted them to be, but the compiler only looked at the first two letters. Great fun debugging that sort of nonsense.
WHAT DO YOU MEAN IT ONLY LOOKS AT THE FIRST TWO LETTERS WHAT
if goto make sense why don't you go to get some bitches
Because "get some bitches" is an invalid instruction