We've come a long, long way together. You changed. Where do we go from here?

Dennis Chiroro

Erlang

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

React I Love You, But You're Bringing Me Down Dear React.js, we've been together for almost 10 years. We have to split contexts to avoid unnecessary rerenders. Most of the time, when a component uses a ref, it passes it to a child component. It's been 10 years, and you still have that flaw.

React I Love You, But You're Bringing Me Down

Very good points. Just my 2 cents, but IMHO some relatively recent react changes are baffling. It feels like there is a very very specific vision that react is trying to pursue, they are not willing to share it but are implementing it nonetheless.
Consider something like ConcurrentMode, it looks good on paper (although not really necessary or essential for most use cases) but it boggles my mind that it wasn’t taken into account what the addition of it means for library maintainers. Take a look at what something like mobx now has to deal with to integrate with react. Is cost/benefit of something like that worth it? We don’t have a say in this, but we do have to deal with the side effects of it being there. It just feels bad. Same thing with <code>useEffect</code> changes in react 18. Or event batching that has a slight tendency to skip some events in some cases and is super fun to debug. And the upcoming offscreen api looks like yet one more thing to deal with without any tangible benefit.
Also the documentation. It feels like Dam Abramov tweets and replies are the new format of react docs and the definitive source of truth.

Alternatives are there. I think the author mentioned quite a few of them. The problem is they don’t have as good an ecosystem. React has some great tools and libraries surrounding it. As for solutions to the problems, well I don’t have them. But I still do understand the author. If you use Vue or Svelte (I have), you will see what the author means.

Actually, the thing he said would not work in solid will partially work in solid, but will lose reactivity, i.e. updates to the text content will not subscribe to the reactive system.
In addition, there is babel-plugin-solid-undestructure that will allow you to use descructuring if you want.

do you have an alternative to react? Or how to solve the problems raised in the article. I don’t know VueJS yet, I don’t know Angular yet… so I don’t have one to compare which is better.

There is no perfect software. It’s reality, accept it. We just use it to make a living.