benface

design engineer

[benface @benface]

@thomaspaulmann @raycast WebKit engineers reading this post

[benface @benface]

@Una @mattgperry @motiondotdev That’s great to hear! What about declarative same-document view transitions? https://t.co/bV8C0BiJeI

[benface @benface]

@dyah10 Pixa! Gimme plz

[bone @boneGPT]

if prompted schizophrenically enough, grok can do other styles than the stuff Elon posts

the slop cannon is showing promise as an art form

[benface @benface]

@cmiller__ @devongovett It might soon: https://t.co/xZVyehH0Wi

[benface @benface]

@wesbos 👀

[benface @benface]

@adamwathan Oh… yeah

[benface @benface]

@jonathandavies @adamwathan That rumor is crazy. No way they release the redesign this year. It’s gotta be March or June 2027.

[Peter Cardwell-Gardner @thefuntastic]

Cadence is out now!

Make music by solving circuits. It took 13 years to figure how to do this well!

Beyond the puzzles:
🐈‍⬛ Pet Ren, the cat!
📜 Enjoy Ren's life philosophy (all text is skippable)
🎹 Use the sandbox to make music
🧮 Or explore turing complete contraptions

[benface @benface]

@DrVexis @theo I find that it’s pretty good at test-driven development, which is a good way to prevent one category of bugs. But real-world / end-to-end testing, especially to detect UI / visual bugs, is definitely not there yet.

[Haz @diegohaz]

The new corner-shape CSS property unlocks exciting new UI patterns.

corner-shape: bevel round;
border-radius: 1em 0 / 3em 0;

[benface @benface]

@boshen_c @github Oxc rules! Keep up the amazing work.

[benface @benface]

Native browser way, any day

[Una 🇺🇦 @Una]

I always *love* @emilkowalski's UI tips! Here's the native browser way to achieve this effect:

View transitions do this "fade-out-while-rearranging" behavior by default. You can also customize the transition with CSS (see demo)

::view-transition-old(*):only-child { ... }

https://t.co/5jMnGF90WB

[benface @benface]

@fractaledmind I believe Tailwind 4 automatically sorts utilities that have multiple declarations/properties before those that have less, so specificity shouldn’t be an issue in this exact case… but it’s probably good to be defensive about it anyway.

[benface @benface]

@adamscochran How is that a “R” in the word “young”?

[benface @benface]

@lukeisandberg @rohitxdotdev @nextjs Hopefully that means “leave the CSS I write alone” and not “silently discard what Lightning CSS doesn’t explicitly add support for” 😄 Thanks for the answer, appreciate it.

[benface @benface]

@lukeisandberg @rohitxdotdev @nextjs Please invest in Lightning CSS. At the moment it’s honestly painful:

- No way to pass options from Next
- Lots of upstream bugs and bad design choices that make it impossible to use modern CSS features because parsing fails

Stop neglecting such an important part of your stack!

[benface @benface]

@adamwathan As long as it doesn’t interfere with folks who (like me) have custom font size tokens in the form of `--text-<number>` (e.g. `--text-16: 1rem`), why not.

[benface @benface]

@DmitryLepisov The Kia one is very clever! I don’t know if I love the way it looks, but the idea is great.