Enough with the bikeshedding! There are much more interesting things about Rust to discuss than this.
Significant indentation is the #1 thing keeping me at a distance from Haskell and Coffeescript.
Any decent editor lets you handle block indentation very simply, and it's typically easy to see what the indentation level should be.
In languages with () or {} I can hit a key to reformat copy-pasted code. In Python I have to do it manually.
When it comes to moving blocks of Python code around inside one source file, then it's a simple matter to hit the plus/minus indent hotkey.
Most editors even let you handle that on a filetype basis, so you can use 4 spaces for Python, and tabs for your C files.
That was supposed to be the compilers job. I am here to do mine.
No wonder so many people hate whitespace based parsing.
What are you talking about? Why wouldn't you have your editor just insert the correct number of spaces when you press the tab key? It's worked fine for all my python work.
Anyway, that's tab vs. space flamewar, best practices flame war, etc.
Long story short, I don't like spaces because editors do not make it as easy to navigate back/forward 4 (or 2) spaces as it is to navigate 1 tab. Most annoying instance of this: what combination of keypresses does it take to get from the middle of a line to the beginning of a line? In Notepad++ it's easy, but it Xcode its cmd-left-arrow then hit right-arrow for every space/tab you need to pass. (Or in general for a Mac text editor cmd-left-arrow, then opt-right arrow, then opt-left arrow, but that doesn't always work right. In TextWrangler it's cmd-left + opt-right, which is better but still slightly tricky hopping from cmd to opt key.)