I didn’t like it, at first
When I first learned about observables I was sceptical about what value I would get from them. Many of the operations they provide are already available with `Array#functions` and ES6 `Promises`.
I usually use React when I write Single Page Apps, and add Redux when I need some sane state management. This works well when you have simple functions that make backend calls and update state when the result is received, however firebase uses WebSockets to give you realtime updates as your data changes. …
After learning about React and redux I found two barriers to my adoption of them:
Like most people, I thoroughly enjoyed redux after learning it. I used it for every project until I grew tired of the amount of boilerplate involved. I started skipping it on some components, and eventually, entire projects. This quickly came back to bite me when I started to see inconsistent state in my applications.
It can also be really tedious to build forms with more than 3 inputs while trying to stay within the bounds of the advice you receive in the React community (don’t use refs, maintain a single source of truth for state etc). …