@housepanther @catsalad The whole point is that the reader gets to choose.
Using spaces tells the reader that you hate them and hope they get leprosy.
@housepanther @catsalad Yes, I was on the losing side of that war. Still not convinced it was the wrong one.
@rupert @housepanther @catsalad Because it wasn't. I was on team "don't care" for quite a long time, but since I stumbled upon this reddit post it is clear to me that tabs are a lot better: https://www.reddit.com/r/javascript/comments/c8drjo/nobody_talks_about_the_real_reason_to_use_tabs/
@danrot @rupert @housepanther@mstdn.goblackcat.com @catsalad If people could actually, consistently limit tabs to block indentation, and never use them for alignment, then I might be convinced, but I've never seen this happen across a team.
The result is, especially in code bases written with a narrow tab stop active, that alignment (i. e. Indentation done that needs to be the same width as some text) will invariably be done with a mixture of tabs and spaces. Change the tab stop and everything breaks in a way that helps nobody, especially visually impaired people.
This is probably a tooling problem as much as anything, but tabs are too easy to get wrong.
@weebull @rupert @housepanther @catsalad Aligning stuff is a horrible idea IMO anyway, since it forces you to change multiple lines as soon as one longer name term is introduced. Get rid of that and you'll have a better code base no matter if you are using tabs or spaces.
@weebull Ah, that's what you meant by that. No, I absolutely don't do that. I would indent it like this:
```
if (
something
&& something_else
&& maybe_something_else
) {
// do stuff
}
```
I just indent by one level, and never align to any text. That breaks to easily resp. needs much rework on potential changes, no matter if tabs or spaces are used.