[HN Gopher] Show HN: Flutter_compositions: Vue-inspired reactive...
___________________________________________________________________
Show HN: Flutter_compositions: Vue-inspired reactive building
blocks for Flutter
Author : yoyo930021
Score : 40 points
Date : 2025-11-06 06:43 UTC (16 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| SquareWheel wrote:
| Should this be a _Show HN_?
| yoyo930021 wrote:
| Thanks
| knifie_spoonie wrote:
| Why not? I'm a Flutter dev, and this might actually be useful
| for me.
| poisonborz wrote:
| -
| exasperaited wrote:
| Is it not the poster's own creation?
| amelius wrote:
| Username checks out.
| wiradikusuma wrote:
| Sounds like MobX (for Dart) https://mobx.netlify.app/ (and GetIt,
| for the DI)
| flr03 wrote:
| How is that better than a ValueListenable/ValueListenableBuilder?
| andriesm wrote:
| 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.
| zigzag312 wrote:
| > I always thought the usability/ergonomics of the Flutter
| framework was slightly poor, but the Dart language itself is
| pretty darn awesome!
|
| I think a lot of ergonomics issues of the Flutter are because
| of Dart language lacking in some areas. Flutter team even
| demonstrated how Flutter is expected to improve when certain
| features land in Dart. (Not sure if/how cancelation of macros
| will affects this.)
|
| I'm (im)patiently waiting for augmentations and declaring
| constructors to be completed. Augmentations alone will help
| with so many things.
| j45 wrote:
| In addition to Dart being pretty neat, Flutter itself has been
| a pretty first class citizen then it comes to documentation and
| developer tooling/experience.
|
| Mobile remains a big surface to integrate and evolve well.
| ttd wrote:
| I've got a pretty large flutter app in production, using just the
| flutter-provided building blocks like ValueNotifier,
| ListenableBuilder, InheritedWidget, etc. It has scaled quite well
| for me.
|
| The main issue IMHO with many of these boilerplate-reducing
| packages is that they feel like one-way trips. Most of them
| require a change to widget inheritance, and they all have
| slightly different syntax and semantics for wiring things up to
| state changes. This means if you get a few years into a project,
| migrating away from the package you chose at the beginning will
| probably be very difficult.
|
| So while the quick example in the readme of this package looks
| simple and understandable, locking in to a third-party library
| makes me nervous, especially if the main benefit is just fewer
| keystrokes. Does anyone have experience or informed opinion here
| that would be willing to chime in?
| ShimbaBumba wrote:
| Wow this looks absolutely great, I love how concise the finished
| solutions look and the concept is easy to understand. Keep it up,
| I'll be following the project's development and would like to see
| performance benchmarks in the future. Great job!
___________________________________________________________________
(page generated 2025-11-06 23:02 UTC)