---
title: "Comment by Netanel Basal on \"Handling global state in React without Providers and boilerplate\" | Hashnode"
description: "Check out Elf"
url: "https://hashnode.com/posts/handling-global-state-in-react-without-providers-and-boilerplate/616163a98e8734462af5f7a8/comment/6161c88718374f2573271cbf"
---

[Discussion](https://hashnode.com/posts/handling-global-state-in-react-without-providers-and-boilerplate/616163a98e8734462af5f7a8)

Comment [Handling global state in React without Providers and boilerplate](https://hashnode.com/posts/handling-global-state-in-react-without-providers-and-boilerplate/616163a98e8734462af5f7a8)

[Netanel Basal](https://hashnode.com/@jsnetanel)

[Oct 9, 2021](https://hashnode.com/posts/handling-global-state-in-react-without-providers-and-boilerplate/616163a98e8734462af5f7a8/comment/6161c88718374f2573271cbf)

Check out [Elf](https://ngneat.github.io/elf/)

[Erik Davtyan](https://hashnode.com/@erikdavtyan)

[Oct 9, 2021](https://hashnode.com/posts/handling-global-state-in-react-without-providers-and-boilerplate/616163a98e8734462af5f7a8/comment/6161c88718374f2573271cbf#reply-6161cbe68e8734462af5fff6)

In my “quest” to building a great state management solution I tried playing around with observables and operators as well. While not as sophisticated as Elf, I had a simple state management with the idea of “useObservable” hook. But in this particular case I tried keeping things as simple as possible. The user of the func doesn’t even know that the state is a BehaviorSubject - using Rxjs is an implementation detail. I have the same func implemented without Rxjs, it was just easier for the article.
