Lots of developers like being declarative right with the HTML. • JSX: Sure is nice to deal with event handlers right on elements. • Framer Motion: Sure is nice to deal with animation declaratively on elements. • Tailwind: Sure is nice to put styles right on the things.
-
Show this thread
-
{/* Can't screw this up! */} <button onclick="activateLasers()">
1 reply 0 retweets 8 likesShow this thread -
Check out how
@tailwindcss makes a case for itself right on the homepage. (video)pic.twitter.com/lq4M410hN714 replies 13 retweets 178 likesShow this thread -
Here's a video of
@framer Motion https://css-tricks.com/video-screencasts/176-working-with-framer-motion/ … where you can see how the animation is applied right to the elements that need it.pic.twitter.com/NhY2D2R8X9
1 reply 1 retweet 25 likesShow this thread -
I don't mind it all, but there has gotta be a limit to it. If a component is dealing with its own data, its own styling, its own animation, its own interactions, its own state machines... I can see things swinging back the other way. Like hey maybe let's split this all up again.
6 replies 2 retweets 52 likesShow this thread
"those who cannot remember the past are condemned to repeat it":https://www.eclipse.org/swt/
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.