malstrom.me
Wake me up when the DEFCON levels have changed. They/them.
https://malstrom.me
https://mastodon.social/@markmalstrom
1,795 posts
493 followers
748 following
Regular Contributor
Active Commenter
comment in response to
post
The Court essentially handed the regime limitless power at the very moment Republicans are criminalizing opposition to their repressive policies.
comment in response to
post
I believe this is Parcel's error (but their RSC support is also very new). I guess I assume this is standard and Next's behavior is not just based on the amount of times I've seen folks on the React team say this shouldn't be allowed, but tbh there probably isnt a codified standard for this behavior
comment in response to
post
FWIW, this does appear to be non-standard behavior for Next
comment in response to
post
Is this new or non-standard? Seems really bad. The reason this was forbidden in the first place was the terrible server/client waterfalls this causes. I’ve seen Dan say several times that this was forbidden.
comment in response to
post
That’s true because Astro components are server components, not isomorphic components. You can’t do that with async React components either. You can, however, use React components as non-hydratable (isomorphic) components in Astro by skipping a hydration directive (the same as no “use client”)
comment in response to
post
Pass server components as children/props to client components. I think that behavior is table stakes for an islands framework, so I didn’t mention it separately. I’m not aware of any island frameworks which can’t do that.
comment in response to
post
Astro can do that too 🙂
comment in response to
post
Idk if this helps at all, but the way I think about RSCs is that they are effectively the same as Islands (in Astro, or whatever else), but they have the added ability to gracefully reconcile global state updates. They are the only islands framework I’m aware of that has that capability.
comment in response to
post
Not really React, but the lack of a standard for JSX and then advancement of the standard so we can have the cool stuff proposed for JSX 2.0 is dismaying to me
comment in response to
post
I refer to all LLMs as "the robot," also helps me to not gender the robots
comment in response to
post
comment in response to
post
OSINT is a 5 letter acronym for a 3 word phrase
comment in response to
post
I wonder how difficult this would be for a more configuration-based routing approach like that of React Router or TanStack Router. I think, theoretically, packages could vend a route config function that points to a file/files in node_modules.
comment in response to
post
At the very least, it should mostly solve the `clientLoader` and `clientAction` problem for RSCs
comment in response to
post
I keep thinking that there’s some hybrid solution between the two which relies on service-worker-side-rendering. Render and re-render your server components in a service worker.
comment in response to
post
Pretty weird to be bragging about collaborating with the NYT on main as if that’s something to be proud of…
comment in response to
post
Today the GOP justices on the Supreme Court endorsed migrants being sold into slavery.
They'll claim otherwise, but that's the reality — today's decision permits Trump to send people from countries around the world to any global hellhole that accepts a U.S. financial incentive.
comment in response to
post
Fisher Price-ass UI
comment in response to
post
Now THIS is very interesting…
comment in response to
post
OmniDiskSweeper is still my go-to app for this
comment in response to
post
WHAT
comment in response to
post
But I think it comes down entirely to preferences and popular convention, I don't think there is actually a correct answer