In the Lord of the Rings fandom there’s a persistent debate whether balrogs, or Durin’s Bane specifically, have wings. The text in Fellowship is ambiguous whether what it is describing are literal wings or something else wing-like.
In the Lord of the Rings fandom there’s a persistent debate whether balrogs, or Durin’s Bane specifically, have wings. The text in Fellowship is ambiguous whether what it is describing are literal wings or something else wing-like.
Spaces, in 2026? Why?
In part, because it forces 2-space tab users to confront the indentation issue above
Also there are no drawbacks… I still hit the tab key to indent (and shift tab to dedent). My editor does the rest.
That’s just not true.
Enlighten me?
You might want to read this: https://www.reddit.com/r/javascript/comments/c8drjo/nobody_talks_about_the_real_reason_to_use_tabs/
(There are more downsides of spaces, but I do not care to list everything. It should be obvious that “there are no drawbacks” is a far too general statement. :P)
The drawback to spaces is that people with vision issues or dyslexia lose the ability to make the code more readable in their IDE by adjusting tab size.
I can’t speak to dyslexia (but in would guess that 4 spaces is easier than 2?).
At my last job we had a default linter policy of 4 spaces across all languages (python, JS, rust, mostly). We also had a blind coder. He never mentioned it. I’d guess screen readers are capable of dealing with it these days?
You can do the same thing with a linter rule, without forcing everyone to see the code in your preferred way.