Nathan Force

@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

@threepointone @jonas What’s DO facets? 👀

@jonas Definitely happening, I think already usable in local dev, getting it to the platform’s going to take a bunch of work (undergoing)

the site with a thousand faces --- there's this line of code that I couldn't have imagined building at any point in my career that's possible today: return new Response(generatePersonalisedPage({user}) every user gets an ai agent assigned to them, in a 15ms radius, with it's own memory and state and whatever. And for your wesbite, for every user, you can spin up a sandbox to generate a page (real code!) based just on their own preferences and vibes (changing over time). Kind of insane. Someone should build this and kill it in the ecommerce game.

@steveruizok Sorry m8 this sounds like an AI feature and the best I can offer you is a new emoji

It would be great if the Safari URL input would recognize that if my url has spaces in it then I’m entering natural language rather than a URL

@devongovett Of course. I wouldn’t describe this as a good UX, really, but it might serve as a stress test for what you’re building. The idea is that the up/down buttons alter the quantity of a given selection. The initial selection is just a regular combobox.

@ForceTheIssue Oh that's something i haven't seen before. Do you have a screenshot you can share of that?

Ok... so when you want a "multi-select" component, what exactly are you thinking of? Send screenshots/links please. 😃

@ryanflorence Currently going from SPA to SSR and updating how we do auth is a pretty big prereq to the story here.

> SSG isn't enough on the search page, we need real SSR! - add `ssr: true` to the config - deploy a server your loaders for pre-rendering now work for SSR too add a loader for the search page and a fetcher form for super easy fetching

Grab Vite, grab React Router, start with a simple SPA - intelligent code splitting by default - efficient data loading with nested route clientLoaders - data updates w/o automatic revalidation with clientActions - pending states and optimistic UI with fetchers