Very interesting experiment. Thanks for sharing! Maybe I’ll find some time to run the benchmarks on my Pixel 7 in the upcoming days.

Man, I didn’t get what I’m looking at at first. But after reading the description and watching the video - pretty amazing!

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.

Ente is as close as you can get to Google Photos with E2EE right now. I recently migrated there. The migration wasn’t painless and involved some scripting to handle albums and duplicates but the service itself is really good. Can recommend!

I really hope this happens. NFC payments are the only thing that keeps me from switching to GrapheneOS. Seeing how the situation with big tech unfolds, it’s not impossible that I will decide to give up this convenience though.

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.

Exactly this worked for me. Just be consistent until it sticks. It can take months, easily. But it works in the end. 10:30 pm - 6:00 am is now baked into my mind and I usually just wake up naturally like 10 minutes before the alarm. I actually love it 😁