Of course, but when indentation has a syntactic meaning the formatter often won’t be able to fix it.

It’s probably more prone to mistakes like that, true. But in practice I really never witnessed this actually being a problem. Especially with tests and review.

Yeah, that’s definitely a good point. But it’s a minor thing. Adjusting indentation takes 2 keystrokes in vim, I barely notice it.

So I’m going to say what I always say when people complain about semantic whitespace: Your code should be properly indented anyway. If it’s not, it’s a bad code.

I’m not saying semantic whitespace is superior to brackets or parentheses. It’s clearly not. But it’s not terrible either.

As someone who codes in Python pretty much everyday for years, I NEVER see indentation errors. I didn’t see them back when I started either. Code without indentation is impossible to read for me anyway so it makes zero difference whether the whitespace has semantic meaning or not. It will be there either way.

Man, I’m just chilling and relaxing after a week of SE work and this resonates with me very deeply

I’m a classic example of an introvert “adopted” by my very extroverted friend. I just want to say that I’m very thankful for them dragging me out of my comfort zone once in a while. I would’ve missed out on a lot of great experiences without them.

I often think how awesome it is that people are so different and how we can help each other by sharing our strengths.

I’m not sure about the exact percentage but I don’t think it’s necessarily that far off. I spend a lot of time reviewing code, designing, documenting, reading documentation. Actually writing code is a cherry on top.

Yeah, no difference whatsoever between those services…

If you’re on the edge right now - do it! Taking care of my body and diet was the best decision of my life.