I always thought the usability/ergonomics of the Flutter framework was slightly poor, but the Dart language itself is pretty darn awesome!

I also rolled my own reactivity interfaces, and made many shorthand functional wrappers for standard things I use frequently to debloat the GUI boilerplate.

My stuff isn't robust enough to consistently live seamlessly alongside regular flutter code or to release for anyone elses use.

I am super stoked to see that I'm not the only one to find the stock flutter framework something that can be improved, and that others more confident than me (and more experienced with other frameworks) are putting things like this out there.

Congratulations and thank you.

I even dream that someone would reimagine the entire flutter framework, maybe just reuse some of the low level rendering and eventing but rebuild everything else on top of that.

Apologies to anyone on the flutter team if I sound too critical, you've put something very useful and difficult out there, but a lot of design choices seem to be mutually inconsistent or just have so many counterintuitive aspects to them, usually justified in the name of performance.

I often find myself thinking I am just not smart enough to figure out the right way to do something with flutter. A lot of abstractions that are hard to get them to work how I want or run into weird corner cases. Many simple things I just ask AI to solve it, and after seeing the solution I can see it is right, still don't understand why my attempt was not.... so I welcome alternative interfaces and approaches.

How is that better than a ValueListenable/ValueListenableBuilder?

Sounds like MobX (for Dart) https://mobx.netlify.app/ (and GetIt, for the DI)

Should this be a Show HN?