MobX vs redux-thunk: What are the differences?

# Introduction
Below are the key differences between MobX and redux-thunk.

1. **State Management**: MobX allows for more flexibility and simplicity in managing state compared to redux-thunk as it does not require actions and reducers.
2. **Asynchronous Operations**: Redux-thunk is specifically designed for managing asynchronous operations in Redux, while MobX does not provide built-in support for managing asynchronous operations.
3. **Immutability**: Redux-thunk encourages immutability of state updates through reducers, while MobX allows for mutable state updates which can streamline development but may lead to potential issues with data consistency.
4. **Boilerplate Code**: MobX generally results in less boilerplate code compared to redux-thunk as it eliminates the need for action creators, action types, and reducers.
5. **Learning Curve**: Redux-thunk has a steeper learning curve for developers due to its concepts like actions, action creators, and reducers, whereas MobX is often seen as easier to grasp and implement.
6. **Community Support**: Redux-thunk has a larger community and ecosystem of middleware and tools specifically designed for Redux, while MobX has a smaller but growing community support.

In Summary, MobX and redux-thunk differ in state management, handling asynchronous operations, approach to immutability, amount of boilerplate code required, learning curve, and community support.