benface @benface

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

6 16 62 7K 23

View Details

benface @benface

4 months ago

@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.

1 0 0 26 0

View Details

Haz @diegohaz

5 months ago

The new corner-shape CSS property unlocks exciting new UI patterns. corner-shape: bevel round; border-radius: 1em 0 / 3em 0;

50 185 4K 229K 2K

View Details

benface @benface

5 months ago

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

0 0 1 65 0

View Details

benface @benface

5 months ago

Native browser way, any day

Una 🇺🇦 @Una

5 months ago

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 { ... }

6 38 533 36K 392

0 0 1 160 0

View Details

benface @benface

5 months ago

@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.

0 0 0 25 0

View Details

benface @benface

6 months ago

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

0 0 4 79 0

View Details

benface @benface

6 months ago

@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.

0 0 1 36 0

View Details

benface @benface

6 months ago

@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!

1 0 2 96 1

View Details

benface @benface

6 months ago

@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.