From my perspective, it has never been a problem.
I've programed some pretty complex logic into construct 3 and I never had to think too hard about the OR block setting.
I am a novice programmer, and I do remember thinking it was weird how it was set up, but after a while dismissed the thought, as all software has a quirk or two.
I do use the Or feature sometimes as well.
This being said, I'd like to propose a 3rd train of thought.
Logical gates are required between EVERY condition in real programing languages.
This would likely never be implemented in construct 3, but if you really wanted to make it the same as traditional languages, the 'OR' and 'AND' blocks would look more like extra condition blocks themselves, with the ability to place one between every condition.
[
+ If sprite.y > 40
Or
+ If sprite.x > 80
]
And
[
+ If sprite.y < 1200
Or
If sprite.x < 400
]
Note that for this to work, you would need to include a way to add parentheses to explain order of operations.
This is how real logical gates work. It's just not how construct is designed.
For me, it quickly became intuitive to know how to turn this logic or any other set of complex logic into a series of events with sub events.
For true 'Or' it's easiest to just make a separate block all together and add any other picking you need to it.
At the end of the day, construct treats the entire event sheet like one huge true or block, resetting picking between each parent event block.
There is not a huge need to bake this behavior into a new feature.
But renaming to ANY sounds like a simple and productive change to me.