Hey Daniel, long-time fan, first time caller. I 100% agree with your point and thank you for publishing this. Here’s a case of using an overflow in responsive design that you might find interesting:

Last year, I helped redesign a complicated web app. It had a lot of legacy features used by paying customers. We did research, prioritized features and cut features but we still had 5–8 actions on some views. We used an overflow menu to contain *only* the actions that wouldn’t fit at the current viewport. On large desktop, no overflow menu. On tablet, most actions are visible with a couple in the overflow. On small mobile, some visible actions but most in the overflow. The actions gracefully fell into the overflow as the viewport shrank(and reverse when it grew). This allowed us to keep the action’s location and order the same on all viewports. The pattern was/is successful but the overflow concept had to be learned by most users.

What do you think about this solution?