ps - please note the light hearted nature of my post
In this particular case we did some user studies and this was one of the pieces of feedback. It didn't apply to everyone, and as you can see from the notes our recommendation is to do nothing. As you have seen from other issues, we do believe in the importance of ease of understanding, though we try not to place it so far above "correctness" that we would do something that others would see as wrong. However, when there are gray areas, I think we do try to make sure that folks can figure out what they need to do without having to look everything up. We have to strike a balance, sometimes correctness makes things more toolable, but it can also make things harder to read quickly. Sometimes correctness is more verbose and causes performance issues when 80% of the time you didn't need that. So it's all about finding the right balance. We hope that you guys can keep paying attention and help us do that
As I said in my post. Just more of a 'please dont' than a 'hey stop!'