Re:Australis Performance Post-mortem Part 4: On Tab Animation
by userbinator on Thursday May 15, 2014 @07:26AM
(#7748811)
Being not a fan of UI animation myself, I agree completely. The fastest way to open/close a tab is to not animate it at all. To me, it's rather odd to see concern about a ~5ms difference in animation speed, when they could've made the whole animation take 0ms quite easily --- the faster an animation goes, the more instantaneous and less animation-like it becomes, and when it gets fast enough, there's no point in having any animation.
I wonder if removing all the user-initiated animation from the UI would improve perceived responsiveness dramatically, since my browser has no tab animation and a new tab appears instantaneously as far as I can tell.
That said, it's amazing in a somewhat shocking sort of way to see just how many layers of abstraction and lines of code are involved in doing something like a tab animation (I notice the article mentions CSS, Direct3D, Cairo, SVG, and OpenGL), and then realise that in terms of human timescale, it's still extremely fast.
I wonder if removing all the user-initiated animation from the UI would improve perceived responsiveness dramatically, since my browser has no tab animation and a new tab appears instantaneously as far as I can tell.
That said, it's amazing in a somewhat shocking sort of way to see just how many layers of abstraction and lines of code are involved in doing something like a tab animation (I notice the article mentions CSS, Direct3D, Cairo, SVG, and OpenGL), and then realise that in terms of human timescale, it's still extremely fast.