Yesterday, I shared some spicy takes. A few were particularly controversial—most notably, that I correct Gif the correct way (with a soft G)—but I also got a lot of emails asking me to elaborate on a few of them.
Today, I wanted to talk about how tabs are objectively better than spaces. This won’t take long.
Tabs let you define how big you want each indent to be, and spaces do not.
Now next time I read anything about why any Python libraries are named what they are named, I’m going to hear Dr Doofenschmirtz voice. Thank you for that.
What, the code is made up by the number of consecutive spaces, delineated by tabs, line feeds, carriage returns (which have different semantics from line feeds) and non-breaking spaces?
Neither tabs or spaces are good. The correct way is to leave no whitespace in the code at all. It’s unnecessary and adds to processing time.
Everyone should aim for 1LOC per commit
“Error: syntax error on line 1”
…shit
Great, no scrolling through thousands of lines to find the right one!
Scrolling to a line number seems inefficient.
Right? I’ll just open the “go to line” box, enter 1 and boom- I’m there.
Or I’ll click the filename.ext:1 in the IDE’s console to jump to the right line. Super convenient not having to scroll vertically anymore.
My program, written in the whitespace language, ruined.
CURSE YOU PERRY THE PLATYPUS!
Now next time I read anything about why any Python libraries are named what they are named, I’m going to hear Dr Doofenschmirtz voice. Thank you for that.
What, the code is made up by the number of consecutive spaces, delineated by tabs, line feeds, carriage returns (which have different semantics from line feeds) and non-breaking spaces?