Too many options out there that are almost the same things, just called differently. I'm even tempted to just write my own, with an API that I like, and use that in all of my projects. But good to see efforts like this to simplify things. I honestly don't like the full BLoC format (event streams) of flutter_bloc, although Cubit is good and simple. I feel like explicit event streams is added convolution and produces code noise more than anything else.
I agree, there are too many options and feel free to experiment for yourself to create the one you prefer. On the other hand, flutter_bloc is one of the best packages for state management, the good thing about it is that it abstracts the stream API (which you can also access if you want) so you technically don't work with streams directly, Cubits are mostly the same as StateNotifiers, just based on streams.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Too many options out there that are almost the same things, just called differently. I'm even tempted to just write my own, with an API that I like, and use that in all of my projects. But good to see efforts like this to simplify things. I honestly don't like the full BLoC format (event streams) of flutter_bloc, although Cubit is good and simple. I feel like explicit event streams is added convolution and produces code noise more than anything else.
I agree, there are too many options and feel free to experiment for yourself to create the one you prefer. On the other hand, flutter_bloc is one of the best packages for state management, the good thing about it is that it abstracts the stream API (which you can also access if you want) so you technically don't work with streams directly, Cubits are mostly the same as StateNotifiers, just based on streams.