Have you seen this:

skip.tools

I’m happy to have it look like a hack if it works but it simply doesn’t work except for the most basic use-cases.

Yeah. Sometimes that works well. But other times I find an older way to do something that works everywhere so I don’t bother!

Also FB had a way to do browser-specific styles so we just did that a lot of the times. Made things easier than manually reverting properties inside of the @supports block

Yes. Please!!

I tried to (ab)use custom elements and shadow dom to do this but it doesn’t actually work properly.

At the time Facebook had to support some browsers that didn’t have support for supports queries!

And my actual code had a fallback for older browsers where the border radius was a static px value. So we’re on the same page there!

I wrote that code before container queries existed. And even today fb supports older browsers that don’t support them.

But when I use this thing these days I reach for container queries too!

Tried it and it didn’t work. So maybe still a wip.

I think the sweet spot is to go so over the top that it becomes parody.

You can do slapstick humor in your thumbnails

True but I definitely see the incentives created by tailwind where devs jump through hoops to avoid the css escape hatch.

- Atomic css solves the scaling problems but comes with its own maintenance burdens
- tools like Tailwind and StyleX solve that.
- I’d argue StyleX and Vanilla Extract are much closer to CSS syntax without all the weird problems of Tailwind.

As to why not just use CSS directly:
- plan CSS is a bit of maintainability nightmare. CSS modules is a thin abstraction that solves that.
- however for larger applications it becomes a performance bottleneck as the CSS keep growing as the app keeps growing

I don’t disagree with Tailwind being annoying, but tbf it suggests you write CSS in a CSS file for unsupported things.

I was more wondering what is impossible or inconvenient in frameworks like React. Because all the new goodness like dialog, popover etc seems just work

I have literally only ever made pancakes at night.

Which underlying browser features exactly do you think is hard to use with any of the popular frameworks?

This is the only good client-side concept they’ve cooked up. I think it would work well within React as well.

Now that React supports ref functions with cleanup, I can see a useEvent() hook making this all fairly manageable.