Teaching the craft of Frontend. ⇢ YouTube.com/@frontendfyi ⇢ frontend.fyi ⇢ fantasticmotion.fyi ⇢ newsletter.frontend.fyi
Amsterdam, The Netherlands
- Tweets 8,850
- Following 1,307
- Followers 2,595
- Likes 5,635
I think this is a very good view at what dev work will look like in a very near future 🤯
Got to talk at @aiDotEngineer conf last week about the need for collaborative AI engineering.
All our current coding agents are single player. We're trying to scale up individual productivity, but creating tons of alignment problems in the process.
We have no good tools for...
1
2
289
Jeroen Reumkens — FrontendFYI retweeted
Wild how far you can push "customizable select" with just #CSS
45
75
1,579
102,741
Do you know if this is a to be expected bug for Popover/Anchor API @Una @bramus fefyi.dev/l7exxieornb
Been struggling with this for a while now, can't seem to find a way to fix this. Issue is that having buttons inside a nested popover, seem to misposition the click/hover target if you scroll down on the page.
Happy to make an issue somewhere too, but was unsure as to where to create it. Thanks!
1
3
1,028
No way, does @loops use AI to create a first few templates based on the provided website? I love that idea. I feels like home straight away.
1
5
448
It feels so wrong. And I think this problem goes for AI in general. I guess I’ll get some backlash for saying this:
It feels like AI “steals” so many things people worked hard on and takes it for free. Whether it’s docs, YouTube videos, free code samples / templates. It’s all stuff people put out on the internet for free since it also was a form of self promotion. Either the person attracted potential new clients / employers because of it, grew their own visibility, or made money by selling a related product.
Now AI just takes all that stuff we put out there for free, and the creators get 0, nothing, nada from it.
I think this will only result in less free things on the internet. Things where we can all learn from. The things that made the internet such a great place.. Creators (or researchers, or any other person for that matter) simple have less and less reason to put out great stuff for free.
🎧 Recorded a new morning walk this morning, hard one to share because I'm sure people will want to roast me for it but have been transparent up until now so publishing it anyways.
1
4
539
Who’s gonna combine these amazing variable fonts by Ulrike Rausch with scroll driven animations? 😍 😬 #nordicjs
2
5
468
Super great talk @EmmaBostian
It’s talks like this that always make me hop back from freelance to being employed and leading a team again. Leading teams brings so many interesting dynamics to the table ❤️ Leading a team as a freelancer is also totally different.
2
8
913
Lovely
lost to wonder on the local daily commute
hop on, enjoy the skies today :)
commuting.to
4
615
Lol. Got kicked out after shooting this video 😬
Top secret preparations happening? #nordicjs
1
3
336
Heading to @nordicjs now. Who’s there? 👀
2
339
Honey wake up, Joma is finally back!
Such a great video again 🤯
youtube.com/watch?v=YRddOEtl…
1
395
With such a title for my daily playlist, there's probably little that can go wrong on a monday morning 🥰
1
272
Jeroen Reumkens — FrontendFYI retweeted
Safari 26 is about to ship a bunch of CSS features I've been eagerly waiting for! 🥳
- Anchor positioning
- Scroll-driven animations
- text-wrap: pretty
Also cool to see contrast-color() land!
webkit.org/blog/17333/webkit…
3
28
219
34,045
Love seeing this become a standard browser api! 🔥
To do this with the (upcoming) interest invoker API, it's 1 line of code:
.parent:has(:interest-source) button {
interest-show-delay: 0s;
}
You have your default delay. Then, you update the interest delay when an element inside of the parent has interest (i.e. hover).
7
399
Jeroen Reumkens — FrontendFYI retweeted
Here's a #CSS study list, 100+ features to checkout from the past ~5 years.
There're surprises in here for even the most knowledgeable front-end developer!
nerdy.dev/cascading-secret-s…
7
32
188
29,034
Jeroen Reumkens — FrontendFYI retweeted
(1/2) I've been using this "follow-the-leader" pattern with CSS anchor positioning quite a bit lately so I decided to write about how to do it!
The TLDR; is you dynamically update the anchor on an event/state, i.e:
.follower {
/* anchor */
position: fixed;
position-anchor: --hovered;
/* transition */
transition: top 0.5s ease;
/* position */
top: anchor(center);
left: anchor(right);
}
.possible-anchor:hover {
/* update the active anchor */
anchor-name: --hovered;
}
6
10
209
25,339
