3 ms·
Ah, but then you commit and someone else pulls the source code down and their carefully crafted N space per tab setting is now worthless since you decided how l
by zaphar 9y ago
Ah, but then you commit and someone else pulls the source code down and their carefully crafted N space per tab setting is now worthless since you decided how long tabs should be for them.
Then they post an angry rant on some mailing list about how forcing tabs to spaces forces people with various reading disabilities into a tabstop setting that makes it hard to read.
And before too long it's devolved into the same old Tabs vs Spaces debate.
- tokenizerrr 9y agoBefore that, your diff looks ugly and you generate tons of merge conflicts by useless indentation changes.
- sergiotapia 9y agoBut... your team just enforces a style. No debate. Two spaces for Ruby I've seen almost everywhere. Two for Elixir, same. Go has go fmt. This hypothetical of different spaces is killed before it happens.
- zaphar 9y agoHaving a style ends the debate yes. Configuring your editor to automatically replace tabs with spaces does not end the debate. It starts it.