Previous discussion on same topic but different posted link: <a href="https://news.ycombinator.com/item?id=17612540" rel="nofollow">https://news.ycombinator.com/item?id=17612540</a>
The transition to CSS transitions seems primitive to me.
<a href="https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations/Using_CSS_animations" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animati...</a> makes it sound very much like a fire-and-forget approach.<p>My concern, also when building UI with React, is that web design is often only interested in end-state of an interface, playing a bunch of fire-and-forget animations to transition between states.<p>The reality, that only games and Apple seem to have embraced, is that it's far more sophisticated for animation to reflect a state that can change at 60 or even 120 frames per second, depending on what the user is doing.<p>This is a great presentation from Apple, Designing Fluid Interfaces, that captures the concept: <a href="https://developer.apple.com/videos/play/wwdc2018/803/" rel="nofollow">https://developer.apple.com/videos/play/wwdc2018/803/</a><p>Am curious: have any web frameworks embraced this approach?
I love the detail-oriented approach to this. Tracking jQuery usage and slowly removing components from their custom jQuery library are both really clever strategies.
> Set up metrics that tracked ratio of jQuery calls used per overall line of code and monitored that graph over time to make sure that it’s either staying constant or going down, not up.<p>Would love to know how this was done.
I don't use jQuery anymore, but damn do I miss the simplicity of fadeIn() and fadeOut(). Trying to do the same with CSS transitions is much more complicated and brittle.
I haven’t removed jquery from my website because it’s probably the least bad code to deal with. With Github’s complicated website, maybe they have bigger fish to fry?