Nmn

When I hear the term “an army of agents”

On the flip side.
- No need for dependency arrays.
- No need to memoize most of the time.
- No need to break up components for suspense.
- No need to have a fancy library or effects for data fetching.

And solid is pretty easy at a basic level:

1. State is getter function (signal)
2. You’re not allowed to read the state in your components. Only create new getter functions that can read the state.
3. Use <When> and <For> components instead of ternaries and .map

Learn Solid.js people. Svelte and Solid are essentially the same with different syntax and IMO JSX > Svelte syntax.

Or I should say the other libraries that popped up when React first became popular. Like Mithril and Cycle.js.

But somehow Remix is the worst attempt at a React-like VDOM component framework I’ve seen so far.

I won’t go that far. I remind me of old react with more awkward syntax.

It would be good to have a way to do conditional imports synchronously.

And bundlers that can handle that kind of thing and serve different permutations of files based on information available during the request.

Apple is getting some well deserved criticism for this.

But aside from that, can we stop using top level await entirely? It makes things so so annoying.

She should do it anyway. And Bernie can maybe be the VP!

Exactly. Unless someone like John Steward runs it’s not looking good.

That’s ignoring the fact that there might not even be another real election to begin with.

Who should run that can actually win?

Moving off React is fine. Not everything needs to be React.

But what they’ve built instead of React is significantly worse than React IMO.

Polanski might have a better strategy.

My observation was purely what i felt watching the videos each of them put out on their own.

I hope y’all get someone good that actually delivers next election.

Just don’t* like how.

I won’t pretend to know enough about UK politics to comment.

I just found it fascinating that you prefer the comms, specifically of Polanski and that’s the one thing i dont like. I like the content of what he’s saying. I just like *how*.

Just interesting.

As an outsider Corbyn came off more genuine. These videos feel performative IMO.

And finally, do you think this is a bloated pile or crap? Cuz I think it feels snappy and easy to use:

next-faster.vercel.app

Also, I thought you were genuinely asking. Devs use the thing they feel will help them build something quickly. They only worry about the quality of the experience after the fact. I’m not saying that’s good or bad. It’s just how these decision are made at profit seeking companies.

I’m not talking about React specifically here. The point is that the solution to React’s problems is either making React itself better or alternatives like Solid.js or Qwik.js

Going back to just the browser standards doesn’t necessarily result in better experiences.

GitHub - rickhanlonii/async-react: The final state of the React Conf 2025 Async React talk. The final state of the React Conf 2025 Async React talk. - rickhanlonii/async-react

Here's the code for my Async React demo:

github.com/rickhanlonii...

Depends how the outer framework is rendering it, but yeah I get it.

I’d rather make a framework-specific wrapper to fix those issues than deal with all the shadow dom weirdness.

💯

Honestly I think with modern web features the need to pull in components built in a different framework should be rare. With dialogs, popovers etc a lot of the things we built manually is available out of the box now.

Get a good styling system and you’re done. (Obvious StyleX plug)

I said that sentence to mean custom elements are “essential”. Having a common interface is obviously good and i think custom elements are the best part of the “web component” spec although i have many issue with it too.

Yup. I think using a custom element is fine as an abstraction for the cross-framework boundary. I don’t think shadow dom is needed in most cases though.

“HTML-web components” would work just fine.

Then we’re basically on the same page!

React used to show state-less components before hooks. Remix only show prop-less components.

Anyway, this is becoming unexpectedly and unintentionally argumentative.

I just think we over-use custom elements and shadow dom because “web components”.

And render scoping is weird to me because as long as you’re in the same framework, you *want* that child to be re-rendered. And if you’re at a framework boundary, you don’t need a custom element to stop rendering. There are all kinds of ways to do that for each framework.

The distribution situation is pretty bad because you still need custom JS and logic for rendering *within* the shadow DOM so it’s just unnecessary overhead.

And if you don’t care about that, using a custom element at only the boundaries makes sense.