getx VS states_rebuilder

the maintainer is a liar (link)

Thanks! I watched the video and he makes some good, rational points. He's definitely right about a lack of maintenance on GetX. It looks like they are looking for more maintainers: https://github.com/jonataslaw/getx/issues/2541

And getx author has shown to be disrespectful and providing misleading information on other packages

https://github.com/jonataslaw/getx/issues/2077 https://github.com/jonataslaw/getx/issues/2067 https://github.com/jonataslaw/getx/issues/1643 https://github.com/jonataslaw/getx/issues/1380

new features are being added in big chunks without any new tests

Don’t believe everything people post here… getx is not dead. So keep using it if you like. Proof: a pretty recent PR for next version … https://github.com/jonataslaw/getx/pull/2008

Sorry guys https://github.com/jonataslaw/getx/pull/2008 😂😂😂

I use states_rebuilder https://github.com/GIfatahTH/states_rebuilder

Unfortunately, states_rebuilder is not one of the "mainstream" state solutions. I assume that's a major factor why there is a relatively low amount of tutorials. That being said, I use it in my app and can only recommend it. The functional injection approach is super simple with clear callbacks when initializing and listening to a state. I found the documentation on github itself to be extensive and explaining everything one might want to know. Did you take a look at the examples e.g. https://github.com/GIfatahTH/states_rebuilder/tree/master/examples/ex_001_2_flutter_default_counter_app_with_functional_injection?

I'm looking at states_builder right now to see if it would simplify the whole state manageent enough to warrant using it in place of Riverpod.

SR example - TODO app https://github.com/GIfatahTH/states_rebuilder/tree/master/examples/ex_009_1_3_ca_todo_mvc_with_state_persistence