kamen

This way people from both sides of the argument can hate you. Win-win!

I can kind of see your point if you’re speaking from a devops/sysadmin’s point of view (i.e. something that would require you to use default editors on the go on systems that you don’t necessarily have control over).

Other than that, a tab’s principal purpose is indentation. One tab is one level of indentation regardless of how it appears. If a tab gets transformed into something else, it sounds like a text encoding problem and indentation would then be just one of (and possibly the smallest of) several possible issues.

I’m speaking from a web dev’s point of view - I’m assuming that I’ll always have my own configured editor on hand and I’ll be able to tell it that one tab is N spaces, sometimes even differently for different file types in the same project. Worst that could happen is that I don’t have a specific configuration and the editor just falls back to the default until I set otherwise. Since I’m working in a team, using spaces for a source controlled project would mean that everyone has to use the same. Having tabs means that everyone can configure it for themselves (assuming editor configs don’t go in the repo).

BMX: free coaster vs cassette.

However many I feel like that day. Sometimes depends on the language and use case - if it tends to be deeply indented, I’d gravitate towards 2.

If using actual tabs, you can change how they appear just for yourself without touching the actual code; the same can’t be said about spaces.

I’m happy that I have only contributed very, very little to that - years ago (maybe 10+) I bought a year’s subscription for their cloud drive - which at the time was I think very good value, because it allowed unlimited photos (including raw files). Needless to say they axed that plan shortly after. Other than that I don’t think I’ve ever bought a physical item from there and I hope this stays that way.