📢 @googlechrome is moving to a 2 week release cycle! More in https://t.co/C8ZQno3u6D
Also, a short history on browser update frequency:
• 2001: MSFT shipped IE6 & didn't release a major update for 5+ YEARS! Safari updated ~annually
• 2010: Chrome commits to 6-week releases & automatic updates. (People called us crazy.)
• 2021: Chrome updates to 4-week releases. (People said it was too fast.)
• 2026: Chrome goes to 2-week releases. (Opinions TBD :)
Release early, release often for fresher features and faster fixes... especially important with AI vuln discovery! 💪
Had one of those intensely vivid pregnancy dreams but it was about responsive UI patterns for supportive context… (weird, I know)
Might write a blog post.
Might have a baby.
Which will come first? 🫣
Big news!
For the past 9 months I’ve been running a fully-autonomous local agent for a pretty complex body building project. And I’m almost ready to deploy (any day now 🙂)!
Wish me luck for the launch 🙏
Design Engineering Tip
Make hover interactions respond to where the cursor actually comes from.
Instead of revealing content with the same animation every time, detect the cursor entry direction and move the image + content accordingly. It makes a simple card feel much more spatial and responsive.
const direction = getDirection(event, ref.current);
const variants = {
top: { y: 20 },
bottom: { y: -20 },
left: { x: 20 },
right: { x: -20 },
};
Neat! Leveraging AI skills is a nice way to make it less tedious to refactor your UI systems to be more modern and flexible. Just be sure to test the results 👀
Excited to publish my first skill: Prefer Container Queries
It makes components respond to their container's width, not the viewport - so the same component adapts anywhere you drop it.
npx skills add flornkm/skills