yoyo930021

4 ms·

1.
by yoyo930021 11mo ago
Sorry about that — I changed the title after reading the comment.
2.
by yoyo930021 11mo ago
Thank you for the support! Regarding performance benchmarks — the framework essentially stands on the shoulders of giants, with its reactivity layer powered by alien_signals. This library originates from one of the fastest reactive implemen
3.
by yoyo930021 11mo ago
I couldn’t agree more.
4.
by yoyo930021 11mo ago
I agreed.
5.
by yoyo930021 11mo ago
I believe there are several improvements in this approach: 1. Interdependent reactive states – multiple dependencies can now be related and work together seamlessly. 2. Automatic dependency tracking – updates are triggered only when minimal
6.
by yoyo930021 11mo ago
That’s true — they both come from the same foundation of reactivity. As far as I know, in the frontend world, there’s even a saying that React + MobX ≈ Vue. However, there are still some key differences: 1. MobX’s reactivity in Flutter is b
7.
by yoyo930021 11mo ago
Thanks for the kind words! I came up with this library based on my own experiences — I had a few insights while using these patterns, and decided to turn them into a library. Flutter chose to design its framework around an approach similar
8.
by yoyo930021 11mo ago
You’re absolutely right — I haven’t found a good way to make the DOM update at a fine-grained level yet. However, I still believe this framework has value, mainly for the following reasons: 1. The setup function behaves just like in Vue 3 —
9.
by yoyo930021 11mo ago
I believe that no matter what framework you use, you’ll encounter similar challenges. Every framework introduces its own complexity by nature — the key difference lies in whether its abstraction can reduce the complexity of building sophist
10.
by yoyo930021 11mo ago
Thanks
11.
Show HN: Flutter_compositions: Vue-inspired reactive building blocks for Flutter(github.com)
45 points by yoyo930021 11mo ago|25 comments