Post

Oh, I didn't realize unsupported, grandiose statements were trying to start a conversation. Does it have the best ecosystem or is it just the most popular with the most options? Why do you believe maintaining 2 virtual DOMs as a reactivity system is the best architectural decision over Proxies?

I think your reaction is a little off. Best *can* indeed mean most popular. It is an important factor if you plan to run your software for a long time. I guess that grandiose statement did indeed start a conversation at least 🤷‍♂️

Never underestimate loyalty to React 😅 I think many people (myself included) find re-evaluating what UI libraries do under the hood daunting, and want things to just work with a decent ecosystem. So they decide that React is still the best based on no evidence.

I would not say no evidence. Is React technically the best solution? No. But in terms of wide-spread support, I would say so.

1 repost0 likes

I thought you ended with “no” again so I chuckled 😄 I should have been more precise: my scope was performance, footprint, UX and DX. Popularity pushes DX into a gray area, but it’s important to be able to shake off the trend and see what’s actually there.

It’s not a simple linear or in some regards even a possible comparison (for example resumability). But we must diversify — for the health of our apps, but also for our community. I want to have frontend devs, not “React devs”.

We’re the ones who control widespread use, that doesn’t just happen. Ironically I’m mainly a React dev, so I’m not biased against it, but after a lot of non-meta experience with it I’ve grown tired. I’d like to see what’s possible elsewhere, and use React for work when I have to.

I agree with everything you said. I actually didn't even write React code before 2024. Before that I was deep into the Nuxt/Vue ecosystem, before that mostly VanillaJS (not to mention the jQuery days and the JS clusterfuck I wrote before that 😁). I mainly gave React and honest shot bc of the