R. Alex Anderson
banner
ralexanderson.com
R. Alex Anderson
@ralexanderson.com
1.6K followers 300 following 3.8K posts
Husband • Dad • Latter-day Saint • Code Poet • Hobby Chef • Spaceship Enthusiast • Serial Optimist • Determined Dreamer Living in Salt Lake City, Utah https://thoriumsim.com
Posts Media Videos Starter Packs
The biggest questions that Remix v3 asks:

- What if we let the browser do more work? (events, signals)
- What if component reactivity was manual? (this.update())
- What if everything had a URL? (Frames)

And perhaps the biggest question of all:

- What if we stopped using `const`?
It's a hard market to go into as well, since there are already so many UI component libraries that _seem_ like equally good replacements for QuietUI. I agree with you that it maybe just needed more time for word-of-mouth advertising?
Its such a perceptual thing that just hardcoding with vibes is as good a choice as any.

I've never heard of a native OS thing. I bet they just hardcode it too.
It's a good time to be a web developer, regardless of stack.
Reposted by R. Alex Anderson
A reminder for Halloween:

Every person trick or treating should get candy, no matter their perceived age. Things are even more scary and oppressive than ever. Let people have one night of fun and whimsy.
Though I'll allow folks to reserve the right to intentionally leave dots unconnected for artistic or teaching purposes. Jesus' parable of the sower is among the worst because he ends up spelling it out, removing room for alternative interpretations.
Explicit > Implicit.

A fine line to tread between being condescending to people who already know what you're talking about, but the audience worth having will appreciate connecting the dots for folks who need it.
Yeah, I've been beating this drum for a while.

bsky.app/profile/rale...
bsky.app/profile/rale...
Here’s an idea: Git for legislation. All laws are stored in a git repo with revision history. Want to submit a bill? Open a pull request. Members of house/senate review the law, and only executive (governor, president) can merge it into master.
Pushing back more, because your idea is compelling.

How do you prevent naive reps from being swayed by persuasive career lobbyists?
How do you compel someone to serve? Seems like you'd need steep incentives (positive or negative) to get someone to upend their lives to be a *shudder* politician.
Reposted by R. Alex Anderson
I just created the “Remix 3 Resources” repo, collecting useful links related to Remix 3.

It has *super* granular links to the Remix Jam live stream for each API, feature and demo, plus a bunch of demo apps and 3rd party integration examples.

github.com/markdalgleis...
GitHub - markdalgleish/remix3-resources: A collection of useful links relating to Remix 3
A collection of useful links relating to Remix 3. Contribute to markdalgleish/remix3-resources development by creating an account on GitHub.
github.com
* Direct DOM manipulation DOES make sense to update the DOM out of the normal render cycle for performance reasons. I can also see situations in Remix where you'd use a stateless component (one that returns JSX, not a function that returns JSX) + a store subscription + direct DOM updates.
JSX + Virtual DOM has some deficiencies, but (correct me if I'm wrong) it's the only declarative way to update UI in a manually reactive system like Remix 3.

Compiled updates don't make sense with manual updates. Direct DOM manipulation doesn't make sense* with declarative UI.
Yeah, I've been doing a bit of research. For the last decade, a lot of the framework differentiation is over two things that are often conflated: Reactivity and "committing" - how to take a declarative UI and turn it into DOM nodes.

Turns out, those two things are closely related, hence conflation
You might be right; you might be wrong.

But I'm confident you're wrong about the stubbornness of the Remix team. If they're gonna sink this ship, they're gonna sink it their way.

I, for one, am interested to see how it all shakes out in practice. Let them cook.
Yeah, seems unlikely to me. I think one thing they're going for is "manual-grained reactivity".
I think the principle remains the same: tanstack.com/query/latest...

The only difference is that I would put a QueryClient in a server middleware and use that to collect all the queries from loaders.

Then a client middleware would hydrate a QueryClient, and then grab the data in clientLoaders.
Server Rendering & Hydration | TanStack Query React Docs
In this guide you'll learn how to use React Query with server rendering. See the guide on for some background. You might also want to check out the before that. For advanced server rendering patterns,...
tanstack.com
It'd be right at home with these lovelies.
Looks like 2007, in a very good way.
But even if you do try to compare them, as I did in the benchmark, their speed is _so close_ that it's practically pointless to optimize.

The speed is a non-issue. (as is the type safety, as we found elsewhere in the thread)

I believe this is all just unfamiliarity bias.