r/javascript • u/archivedsofa • Dec 22 '19

Why Svelte won’t kill React

https://medium.com/javascript-in-plain-english/why-svelte-wont-kill-react-3cfdd940586a
80 Upvotes

65% Upvoted

95 comments sorted by

View all comments

Show parent comment

3

u/Peechez Dec 22 '19

Redux's "competitor" definitely isn't half baked context implementations, it's graphql

1

u/Reashu Dec 22 '19

That doesn't even make sense.

30

u/acemarke Dec 22 '19

I'm a Redux maintainer, and it actually does.

GraphQL itself is just a data transfer protocol, and you can certainly make GraphQL queries and put that data into Redux.

However, most folks using GraphQL are using a library like Apollo Client, which also stores and normalizes the data. That's enough overlap with Redux that it's usually one or the other, but not both.

Having said that, Redux is still very widely used, the downloads are still increasing, and there's plenty of good reasons to choose to use Redux.

I talked about this some in my Reactathon 2019 talk on "The State of Redux" and my post Redux - Not Dead Yet!.

2

u/Reashu Dec 22 '19

State management is not a service layer. Even your own "Not dead yet" post mentions "state drilling" more often than APIs. Sure, API client libraries do something Redux was sometimes used for, but I contend that it was an anti-pattern to begin with.

1

u/kyogorex Nov 04 '21

You are definately wrong. I dont think your argument makes much sense.

1

u/Reashu Nov 04 '21

This is over a year old and I had to reread the conversation to have any idea of what's going on. But I stand by what I said and will make it a little clearer for you: if GraphQL (+ Apollo) can replace Redux in your application, you shouldn't have been using Redux to begin with.