The use of yes/no confirmation dialogs seems very 1990s. For things that really don't matter, and are just as easy to undo as they are to confirm, it just adds a step for everyone who got it right the first time as well as the few who accidentally clicked "like" or whatever. There's no consequence to accidentally liking something.
Confirmations have their purpose. For me it's when there are greater consequences for a mistake, such as 1-click ordering. I'd rather go to a screen which shows not only the cart contents but also the card used, shipping address, etc because I have multiples of those. That screen is basically a beneficial confirmation dialog. Deleting or moving a lot of files, a dialog is useful especially if it lists the files you're acting on and the destination. MacOS, when you want to shut down, does display a confirmation dialog but it times out, so you can have a 1-click shutdown or restart if you just walk away. Sort of a smarter confirmation dialog.
Animations can serve a useful purpose. When a screen element jiggles because it needs your attention before you can proceed, that's useful and intuitive. The animations here are pretty benign and don't bother me, though, because they don't give me the feeling that they're wasting my time. They're just kind of cutesy.
At this point, though, I think users would prefer that dev time was spent on the gear database rather than the interface.