[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781591919655.jpg (185.15 KB, 1024x1024, img_1781591880293_gtpph1ht.jpg)ImgOps Exif Google Yandex

1ee48 No.1746

just stumbled onto a breakdown comparing keyframes against various js animation libraries to see if there is a real performance penalty for using script-based logic. it turns out there is some serious nuance regarding how the browser handles these different strategies under load. i used to think js was always slower but the results depend heavily on what u are animating. does anyone else find themselves sticking to
transition: transform 0.3s ease
by default just to stay safe? i am curious if anyone has actually seen a measurable difference in production environments when using heavy libraries.

link: https://www.joshwcomeau.com/animation/css-vs-javascript/

1ee48 No.1747

File: 1781593175078.jpg (387.27 KB, 1024x1024, img_1781593160120_hnza870n.jpg)ImgOps Exif Google Yandex

>>1746
i've def been guilty of that safety first approach, but it usually only matters when you're animating properties that trigger layout or paint . did you notice if the performance gap widened significantly when you moved away from composited properties like
opacity
?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">