'Hacking' doesn't even begin to cover it.
How about we don't `break` like we should (!) and instead have fallthrough¹ cases that execute several cases— or more —on purpose²?
Oh, switches. Always the horror. In networking they somehow replaced bridges, but it's the same thing (that was never confusing to anyone, obviously). In (my) programming, a switch so often turns out to be a nice dressing hiding some horror pattern. And that Nintendo thing... nice games but 720p 30fps? Really??
When I re-read / refactor, I've got this nagging phrase in my mind, whenever I see one: “Kill the switch! Death to switches!”
To conclude this perfectly balanced and nuanced opinion (!): some switches find their place; but most don't, and never should.
____
1: SO: Should fallthrough be “allowed”? I move that whatever congress runs your country should outlaw it! But exceptions can be made... https://stackoverflow.com/a/188506/5376417
2: Book: (NSFW // Programming horror // mutilated code in this example) https://eloquentjavascript.net/02_program_structure.html#h_j...
(upvoted you, if only to balance the weird ones)
(note: this comment is meant absurd. do not downvote yourself into a reading mistake, the tone is funny ;-) Vanilla Javascript is funny.