DEV Community

Discussion on: The Splintering Effects of Redux

Collapse
 
bytebodger profile image
Adam Nathaniel Davis

dev.to/bytebodger/react-is-eating-...

Why I find React compelling (and why it can be so frustrating) is summarized in my latest post.

IMHO, SSR is much faster/easier to build. But I also believe that the end product is inferior. Full roundtrips to the server are definitely not where I want to be investing my dev skills in a modern context. Obviously, there's still a firm place for SSR, but not in the kinda apps I wanna build.

I did take a look at the Todos implementation. One thing that strikes me is that I can write that same app in React for nearly the same LoC. This isn't meant to argue for React or against Stimulus. But this is what led me to write a full blog post as a kind of "answer". Because React - in the form we often see in enterprise apps, is much more bloated and harder/longer to write. But it doesn't have to be at all (and that's frustrating to me). There's no reason why that Todo app can't be just as small-and-efficient as the Stimulus version. But usually, once the React community sinks their teeth into it, it will be indeed be much larger and much more obtuse.

Collapse
 
leastbad profile image
leastbad

That's (almost) all fair; I do think that it distorts the conversation when you suggest that SSR == full roundtrips == inferior UX. Turbolinks and StimulusReflex completely eliminate the full roundtrip argument, which I believe demands you reconsider your own internal algebra on the pros/cons.

Anyhow, thanks for replying and checking out SR.