darkwiiplayer/blog
1
0
Fork 0
Code Pull requests Activity

Update tabs vs. spaces post

Browse source 
Mostly rephrase things I didn't quite like anymore
This commit is contained in:
Talia 2022-06-22 11:07:20 +02:00
parent d3e60e8283
commit 7da300bb8f
1 changed files with 10 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
Rants/Tabs over Spaces.md
View file

@ -16,62 +16,48 @@ In this post, I will do my best to explain why **tabs** are the right choice, no
First of all, I want to define the scope of my argumentation: I am referring to **indentation**, not **alignment**. First of all, I want to define the scope of my argumentation: I am referring to **indentation**, not **alignment**.
The former depends on semantics, the latter on word lengths. For obvious reasons, using tabs for alignment is not possible; whether alignment should be a thing at all (hint: it shouldn't) or how it should be achieved is a different debate and irrelevant for this article. The former depends on semantics, the latter on word lengths. For obvious reasons, using tabs for alignment is not possible; whether alignment should be a thing at all (hint: it shouldn't) or how it should be achieved is a different debate and irrelevant for this post.
# Semantics # Semantics
The most puritan argument for tabs is probably the semantic information they add to the code. I have never seen a real-world example where this matters, but as programmers we often like to obsess over using the right "thing", be it a HTML element or an ASCII character. The most puritan argument for tabs is probably the semantic information they add to the code. I have never seen a real-world example where this matters, but as programmers we often like to obsess over using the right "thing", be it a HTML element or an ASCII character.
Just as with HTML, I suspect this might be relevant for users of screen-readers; if so, I'd like to hear about that in the comments.
# Consistency # Consistency
The main argument I've heard defending spaces is that code looks "consistent" everywhere. Whether you post your code on Stack-Overflow, GitHub Gists, or on your blog; it will always be indented by the same width. The main argument I've heard defending spaces is that code looks "consistent" everywhere. Whether you post your code on Stack-Overflow, GitHub Gists, or on your blog; it will always be indented by the same width.
In the next section I will explain why that is actually a bad thing, but first I'd like to point out that this doesn't have any benefits either.
Code is not visual art. The indentation width doesn't alter the codes meaning in any way and, unlike with alignment, changing it doesn't break the visual layout of the code. Code is not visual art. The indentation width doesn't alter the codes meaning in any way and, unlike with alignment, changing it doesn't break the visual layout of the code.
There is no reason whatsoever why another user reading my code on the internet should read it with the same indentation width that I wrote it in. **There is no reason whatsoever why someone else reading my code should experience it with the same indentation width that I wrote it in.**
# Customizability # Customizability
On the contrary: forcing the reader to use the same indentation width as the author only takes away from their ability to read the code the way they want. I personally prefer a tab-width of three spaces. Two is just barely too short to follow through deeper nested blocks of code. Four is one more space-width than I need.
As an example: I personally prefer a tab-width of 3 spaces, because 2 is just barely too short to follow through deeper nested blocks of code and 4 is one more space-width than I need, and thus one wasted character of line-width per indentation level. So the question is: Why would *you* have to read my code with such an awkward tab width, just because to my uncommon taste <!-- unintentional skyrim reference --> that seems like the right value?
So the question is: Why would *you* have to read my code with such an awkward tab width, just because to my uncommon taste that seems like the right value?
The answer is, of course, you shouldn't. You should be able to read *my* code the way *you* prefer to read it. The answer is, of course, you shouldn't. You should be able to read *my* code the way *you* prefer to read it.
Just like we don't expect readers to use the same editor, with the same colour-scheme, the same font and the same font-size as us, we shouldn't expect anybody to use the exact same indentation-width. **Everyone should be able to read code with their own preferred settings.**
# Accessibility # Accessibility
So far I've looked at customizability as a convenience feature. I *like* 3-space indentation more, so I *want* to read code that way. So far I've looked at customizability as a convenience feature. I *like* 3-space indentation more, so I *want* to read code that way.
What I haven't mentioned is how for some programmers, the right indentation width can make a huge difference in how well they are even able to read the code. But for some people it goes beyond just preference.
There have been countless posts of visually impaired developers. For some, 2 spaces is just not enough indentation, making it unnecessarily hard to read code, others might need to use very large font sizes, and prefer shorter indentations to save screen space. I've seen posts and comments of quite a few developers with poor eyesight. For some, 2 spaces is just not enough indentation, making it unnecessarily hard to read code, others might need to use very large font sizes, and prefer shorter indentations to save screen space.
And as I mentioned above, I don't even know how well screen readers deal with spaces as indentation, and would love to hear about it of anybody reading this has any experience with that.
# Consistency (again, but differently) # Consistency (again, but differently)
This is by far the most ridiculous reason, or group of reasons people make to argue for spaces: This is by far the most ridiculous reason, or group of reasons people make to argue for spaces:
Projects indented with tabs, so the claim, cause additional work when people contribute code that is indented with spaces, requiring additional moderator intervention. Projects indented with tabs—so the claim—cause additional work when people contribute code that is indented with spaces, requiring additional moderator intervention.
Needless to say, this argument works exactly the same both ways, and if anything, says more about the typical space-user than the typical tab-user. Needless to say, this argument works exactly the same both ways, and if anything, says more about the typical space-user than the typical tab-user.
Regardless of preference, in the age of linting tools and CI pipelines, this is just not an issue anymore. We can automate the process of checking indentation, or even have it fixed automatically. Regardless of preference, in the age of linting tools and CI pipelines, this is just not an issue any more. We can automate the process of checking indentation, or even have it fixed automatically.
# Conclusion # Conclusion
There is not a single good reason to prefer spaces over tabs. The whole space-indentation mythology is nothing but hot air and false claims. There is not a single good reason to prefer spaces over tabs. The whole space-indentation mythology is nothing but ridiculous non sequiturs and false claims.
-----
Do you disagree with my position? Let me know!
I'd love to hear additional arguments for or against spaces in the comment section :D