a
about
blog
register
login
🇳🇴 Nodic (english)
Standards
🇵🇱 Polish
Español
France 🇫🇷
中文 (Chinese Simplified)
Türkçe
Overview
Premises
Arguments
Fallacy Reports
Tabs are better than spaces for indentation (programming)
Use the right tool for the right job: tabs for indentation, spaces for alignment (i.e. tables).
Tabs are better than spaces for indentation (programming)
I have responsive CSS to set the tab width of code examples on my website. On mobile phones, I set the tab width to 2, but on other devices I have it set to 4 (my preference). This ensures code fits on small screens.
Tabs are better than spaces for indentation (programming)
On my laptop screen, in the Atom text editor, I have tab width set to 2, and on my wide desktop screen, I have tab width set to 4. It allows the code to be readable both displays while maximising screen usage.
2 supporter.
Python is better than Ruby
This assumes that simple syntax makes complex code easier to read. I'd argue that Ruby's more comprehensive semantic model allows for complex code to be easier to read because the intent can be expressed more clearly.
Tabs are better than spaces for indentation (programming)
Some editors don't support backspace correctly when using spaces for indentation. You are still required to press backspace N times when using N spaces per level of indentation.
2 supporter.
Tabs are better than spaces for indentation (programming)
Tabs can visualised in a way that reduces errors. Conversely, it's common to see code using spaces for indentation with off-by-one whitespace errors.
4 supporter.
Tabs are better than spaces for indentation (programming)
Tabs carry more semantic information than spaces. Case in point: Converting from tabs to spaces is easy but going back the other way is hard (information is lost).
3 supporter.
1 fallacy report.
Irrelevant Conclusion