Thanks, Yoav! I think this approach is nice for small applications and I have used it in production before. One of the reason’s I’ve shied away from it is because it’s not widely adopted/documented and any good idea without proper backing from a community depreciates in value (I feel guilty introducing too many custom solutions to my team). I think Redux would be great if there wasn’t so much misinformation and anti-patterns built around it. Most people simply don’t know how to name and think about actions (actions really should be called events IMO). I think the main problem with my approach here is it’s not optimized to prevent unnecessary re-renders and it doesn’t benefit from the natural decoupling that comes with pub-sub event patterns, but I think it’s still valid and there are some good design takeaways from the article.