Nick Saunders

@samuelcook This happens to me too!

Anyone else feel like a scroll event should focus the window/app on which the scroll occurred? Probably 10x a day I'll switch my "literal" brain focus to another window, start scrolling, and then type a command, only for that command to execute on the prior window I was using.

@BrandonMathis @sickdotdev I would imagine that memorizing the syntax (or constantly looking it up in the docs) takes a lot of work.

@sickdotdev Tailwind sucks and provides 0 value in frontend development. Defenders are just too lazy to actually learn css.

a tech opinion you can defend like this?

We believe styling should be expressive, colocated, and predictable. Today, we take that mission a step further with a new look designed to be as modern as the code CSS Hooks enables you to write. Experience the evolution in the first reply. 👇

design tokens are for designers

New framework strategy: "We've fixed all of React's problems! But to make sure you feel at home, we're keeping JSX." What nobody realizes is that JSX is an anchor, not a lure.

Just finished migrating the @remix_run v3 bookstore demo from JSX to Renuel. It now runs natively in Node.js without tsx.

@asheshjyotii div( { id: "parent" }, div({ id: "child" }, h1$("I'm h1 tag"), h2$("I'm h1 tag")), div({ id: "child2" }, h1$("I'm h1 tag"), h2$("I'm h1 tag")) )

React without JSX is HELL!

After ditching JSX, polymorphic components are no longer a headache. Aside from terser syntax, you can avoid prop collisions, excess props, and other pitfalls of the `as` and `asChild` props.

jsx is great until you hit a .map()

The @remix_run team gets it: "Designing for bundlers/compilers/typegen (and any pre-runtime static analysis) leads to poor API design that eventually pollutes the entire system." Can't wait to check out v3!

TIL Pigment CSS is on ice because extra build steps are too much of a burden. Wishing @MUI_hq the best in their search for a low-friction styling solution with RSC support.

just found a new pattern for polymorphic components that doesn't compromise on type safety _or_ convenience

no css no jsx no idea why y'all make it so hard

quick update regarding @CSSHooks NO, it's not dead. a lot of people are wondering why it doesn't receive daily updates like all the other styling solutions out there... simple - because it "just works". no need to mess with it.

@asilvadesigns Why not?

*inhale.... you don't need a component library

@Mega_Jules Thanks for the update! I keep forgetting that `URL.parse` is still too new. The latest version of Safari has support I think, but it seems most people haven't been upgraded yet...

@agilecoder Yes I am. It's working now though!

In my first blog post of 2025, I explore a few reasons why the CSS cascade is generally something to avoid and what you can use instead. Please let me know what you think! nsaunders.dev/posts/cascade-…

@Mega_Jules Thanks for letting me know! Are you using Safari?

@agilecoder Would like to read it but I'm getting an error boundary