Nathan Force

@devongovett is there a preferred place/method for RAC feature requests? I know you’ve asked on X in the past and there are some issues/discussions on GitHub. We’ve got a few to propose and could even possibly contribute.

@steveruizok Which department will work down in the catacombs?

ok codex turn these floor plans and realtor photos into a blender model. now add these desks [link]

@ryanflorence Fair enough. Could easily imagine them warning during dev if the element already has some value set or other precondition is violated.

I mean ... Remix is new so even I don't have enough experience to say this definitively but I don't think that's a concern in practice. It's hard to imagine why you're applying two mixins that both want to mess with the same attribute. But if they do, they can first inspect if the element has an attribute already or not and avoid changing it. Last mixin wins though (the mix array order is relevant) As for events, it's just like addEventListener, any mixin can add a click event without needing to manually compose them together like a react component wrapper (call props.onClick, check event.defaultPrevented, call your own onClick or the weird useComposedEvents(props) stuff we all do) I don't know what kinds of events are fundamentally incompatible with each other, but if they do exist, I don't know why you'd be applying those two mixins to a single element.

Remix 3 mixins are like components for element behavior. One thing I love about them is it gets rid of the awkward as/asChild composition dance.

@ryanflorence Maybe like two mixins that add event handlers to the same event that are fundamentally incompatible. Or two mixins that both try to apply aria attributes and focus management to an element but in different ways and end up fighting each other.

@ForceTheIssue I have idea about what you mean but outside of attribute conflicts (like two mixins want to change `href`) what do you mean?

@cnakazawa A black box?

Today we are launching three things: * a web bundler: github.com/vitejs/vite (v8) * a task runner: github.com/voidzero-dev/v… * a ████████ Get it?

@devongovett do you use internationalized/date exclusively for date work in you projects or do you pair it with something like date-fns, dayjs, Temporal etc?

@devongovett Nice! Does TreeSection change anything with regards to selection? Are entire sections (de)selectable?

New React Aria release! ✅ Multi-select ComboBox with customizable selection rendering (e.g. TagGroup) 🏝️ Tree sections – create labeled groups of items 💯 Better NumberField paste handling 📆 Improved Calendar month and year dropdown behavior 🐞 Lots of bug fixes!

@jaredpalmer Totally. Feels like an overemphasis on the whole “one shot” part. I’m more than okay to accept an incomplete solution so long as the chunks are logically split. It also makes reviewing the output much more difficult because the core change is lost in the sauce.

It feels like current generation of coding agents are overfit to make code run (and render) successfully on every prompt. Too often, they emit “fallback” behavior and avoid breaking changes as a reward hack, sometimes not even telling you about it.

@devongovett Won’t be mad if you add “Event calendar grid with time slots”

Examples

@devongovett Yessss down with ephemeral UX

Interesting: GitHub is removing all toasts from their UI due to usability and accessibility issues. I agree they tend to be overused, probably because they’re so easy to implement. There are often better patterns like inline confirmation/errors. primer.style/accessibility/…

@kepano Based on this post and your episode of @DialecticPod, I feel like you might appreciate this account instagram.com/oddandordinary…

my current obsession is doors

@jaredpalmer @github Actually just want a more robust code metadata model in general, but this is a start.

@jaredpalmer @github github.com/orgs/community…

How can we make @GitHub Pull Request and code review experience better?

@jaredpalmer @github Expose hidden content to browser so that cmd + f still works as expected

@jaredpalmer @github Allow before/after image slider in description/comments or some other first party image diff support

@seflless Looking more and more like the tool I’ve wanted for ages. How are the screen connections determined?

With Decode you can view as many app screens as you need. Enabling you to review your working app as easily as reviewing a Figma file, but with Claude Code immediately apply your suggestions. Get early access: decode.dev

We built Claude Code into a browser & whiteboard! It's called Decode @decodetool It’s the fastest & best way to give UX feedback to Claude Code while coding locally & enables it to review & test changes itself See thread👇to learn how whiteboards makes it an even better browser

@ryanflorence @devongovett There’re all kinds of hit checks and device/family specific conditions in their usePress hook iirc

@ForceTheIssue @devongovett yeah, it normalizes them all to essentially what spacebar does on a click event down -> up -> dispatch so: pointerdown -> pointerup -> dispatch keydown enter -> keyup enter -> dispatch (no repeat) keydown space -> keyup space -> dispatch Devon am I missing anything there?

I vibe coded most of Remix UI stuff (we only started on them three months ago) Now we're refining the APIs of the events package and writing by hand (with assistance of course) Once published, you'll be able to use semantic, stateful Interactions anywhere, including React!

@steveruizok Hyped for tldom

progress on my new imperative TypeScript framework