4 ms·
Maybe I'm just getting old, but I found most of the animations in this article to go too fast. I couldn't tell what was happening, couldn't tell what I was supp
by joemi 4y ago
Maybe I'm just getting old, but I found most of the animations in this article to go too fast. I couldn't tell what was happening, couldn't tell what I was supposed to be looking at.
- grimgrin 4y agookay ignore everything you saw and just conceptualize: 1) list of text 2) input to filter the list down. see: list gets tinier
- TacticalCoder 4y ago> Maybe I'm just getting old, but I found most of the animations in this article to go too fast. It's not that you're getting old and it's not that it's "too fast". The problem with many animations like this and why they make no sense whatsoever is because they cycle without adding a little pause... So you have no way to know when it's beginning and when it's ending. It's endemic on Github. Some .gif files are properly done but IMO most don't explain anything, only add confusion and would be better served by three or four screenshots. There are poor UX and then there are these kind of cycling .gif files.
- ornornor 4y agoI wish asciinema was used for these instead of the gifs in article, GitHub, etc.
- chillpenguin 4y agoI agree, those animations were way too fast. I'm only 30 so it's probably not an age thing!
- berkes 4y agoMaybe "speed" is something they want to convey? An animation that shows a very slow pace might communicate that the tool is slow too.
- joemi 4y agoSpeed, sure. But I highly doubt that speed beyond comprehensibility is what they intended to convey.