My personal preference is the opposite: I came to hate presentations that use animations. Any presentation that can't be presented in static pdf is a presentation I'd rather miss.
My personal preference is the opposite: I came to hate presentations that use animations. Any presentation that can't be presented in static pdf is a presentation I'd rather miss.
Then there's the terrible animations—a gif of a meme playing in an infinite loop. These make the slide unwatchable for me.
Showing 10 lines of code on a screen at once is a surefire way to have the audience either not read/understand it or to read it, but ignore what I'm saying. So I like to build up a slide full of code by starting with a couple line (eg the function definition), then adding a few more, then a few more, and then the whole thing. Subtly animating the new line in is a great way to highlight what's changing. Double-so if I'm reordering lines. Otherwise the code is just flashing from one state to another and it's not always obvious what happened.
Even better, I sometimes want to walk through the execution of code. I love having a red arrow highlighting what line we're on, and animating it between positions is a good way to highlight that we're moving from one thing to the next, especially with non-linear jumps (like from the end of a loop back to the top).
Animation is an easily-abused tool, but it's also a powerful one.
I'd probably do something similar for stepping through code. But at that point it's a quasi-animation (albeit, one that can still be understood by pdf slides).
I feel the complete opposite - if the presentation can be distilled in a static PDF, I'd rather just read the blog post. The entire point of a presentation is being engaged with the speaker to me.