![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemdro.id/pictrs/image/6d56629c-a7b1-465d-8b58-ad77926e3a41.png)
Very interesting experiment. Thanks for sharing! Maybe I’ll find some time to run the benchmarks on my Pixel 7 in the upcoming days.
Very interesting experiment. Thanks for sharing! Maybe I’ll find some time to run the benchmarks on my Pixel 7 in the upcoming days.
Of course, but when indentation has a syntactic meaning the formatter often won’t be able to fix 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.
I don’t have any answers unfortunately. It looks like the implementation is just half-assed because making it good isn’t actually in Google’s interest.
If you install one of the supported apps (e.g. Ecosia) it appears as an option in the menu. I didn’t find a way to use FF yet.
Software development and computer stuff in general is my passion. I enjoy doing it as a hobby even after doing it at work. If I didn’t have to work for money, I would probably work on some open source software. In fact that’s kinda my dream / goal - achieve financial independence and work on open source as I please.