Yes, I know :) . Having learnt to program some microprocessors, I love how everything is evaluated in terms of jump-if-zero, jump-if-not-zero. Well, even some cracks to copy-protection from older games (dating myself here) was just a single change from a hex 74 to a hex 75 somewhere in the code.

And, sometimes, even in small programs, knowing where you are after some jumps is a messy thing.

I just don't have all that rant against jumps (or goto's). I know where they live, what they eat, when they are useful and when are not. :)

Nah, hardware is more like dataflow or flow-based programming. Maybe functional programming, too. Goto is jumping to arbitrary, imperative code in RAM with an address and no regard for current state. There's possibly something in hardware like it but default stuff I saw in books were more like FSM model focused on data flows.

You're right that I should have said "At the level of the software as understood by the hardware" or something instead.