Only read through the docs. Never used in a project because watch_it promotes creating state objects disconnected from the widget tree and commands are a bit too convoluted (but that might be caused by the current docs structure?) I like the commands instances being callable, clever 👏
November 30, 2024 at 8:03 PM
Only read through the docs. Never used in a project because watch_it promotes creating state objects disconnected from the widget tree and commands are a bit too convoluted (but that might be caused by the current docs structure?) I like the commands instances being callable, clever 👏
We don’t, BLoC will likely stay my go to choice for professional work, but I have a few ideas I wanted to validate with other developers.
We need to innovate — as Dart itself evolves so should our approach to old problems, but we don’t want to see experiments on our stable solutions, right?
We need to innovate — as Dart itself evolves so should our approach to old problems, but we don’t want to see experiments on our stable solutions, right?
November 22, 2024 at 6:31 PM
We don’t, BLoC will likely stay my go to choice for professional work, but I have a few ideas I wanted to validate with other developers.
We need to innovate — as Dart itself evolves so should our approach to old problems, but we don’t want to see experiments on our stable solutions, right?
We need to innovate — as Dart itself evolves so should our approach to old problems, but we don’t want to see experiments on our stable solutions, right?
True, the syntax is similar to the one that creates an instance but it’s clear enough to me what’s happening.
I’m in the process of creating my very own state management library, I can already tell you won’t like it 😀
I’m in the process of creating my very own state management library, I can already tell you won’t like it 😀
November 22, 2024 at 2:25 PM
True, the syntax is similar to the one that creates an instance but it’s clear enough to me what’s happening.
I’m in the process of creating my very own state management library, I can already tell you won’t like it 😀
I’m in the process of creating my very own state management library, I can already tell you won’t like it 😀
For me, as a former JS dev, it was _unnatural_ to not have deconstruction prior to Dart 3. It’s a matter of preference really — I find the other notation a bit verbose with many fields to access.
November 22, 2024 at 5:30 AM
For me, as a former JS dev, it was _unnatural_ to not have deconstruction prior to Dart 3. It’s a matter of preference really — I find the other notation a bit verbose with many fields to access.
True, but I stopped caring about it once I read its description a while back anyway 😀 0,5M as the top liked package vs. 3,6M of provider or yours 1,5M on get_it is staggering
November 20, 2024 at 6:40 PM
True, but I stopped caring about it once I read its description a while back anyway 😀 0,5M as the top liked package vs. 3,6M of provider or yours 1,5M on get_it is staggering
Yup, I always though that eye candy widgets got relatively a lot of likes because of the wow effect, while essential, low-level, solid tools, were being popular in silence as not many devs even think to interact with the pub.dev page other than reading through the docs.
November 20, 2024 at 6:12 PM
Yup, I always though that eye candy widgets got relatively a lot of likes because of the wow effect, while essential, low-level, solid tools, were being popular in silence as not many devs even think to interact with the pub.dev page other than reading through the docs.