Email or username:

Password:

Forgot your password?
Top-level
weebull

@danrot @rupert @housepanther @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.

4 comments
Meow :verified:

@weebull @danrot @rupert @catsalad That's why they need to be standardized across the board at a nice even number like 4 spaces. Until that happens, spaces are definitely the way to go over tabs.

danrot

@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

@danrot @rupert @housepanther @catsalad I agree for separate statements, but you don't align to parenthesis in multiline statements?

danrot

@weebull yeah, but I don't see how tabs are a problem here 🤔 Or I don't understand what you mean by that, care to share an example? All I know is that I never ran into issues with tab code bases.

Go Up