I just want to ask why did u guy switch from redux-saga to redux-thunk in 2.0 beta version? Any reasons to switch to thunk? Just curious.
Hello MemoChou,
There are two main reasons:
- We found that saga requires too much boilerplate, especially when socket.io is involved.
- We had huge issues and delays with the Envato item review process, as their automated analysis marked a “while (true)” cycle as wrong. Now, 99% of the time such a cycle would be wrong, but not when using redux saga event channels. We had a tough time explaining this to the reviewer, so it just makes sense to avoid future discussions by removing saga as a whole.
Have a sweet day!
1 Like