Rebaz Raouf

189 posts

Rebaz Raouf

Rebaz Raouf

@rebazdev

Full time CEO @swiftybase_pro | Building the future of no-code backend development

Присоединился Ağustos 2017
529 Подписки152 Подписчики
Rebaz Raouf
Rebaz Raouf@rebazdev·
@shiweidu Great, thanks for adding that. I have a specific app that requires Deno, so this makes it easier to switch runtimes.
English
1
0
2
52
Luke
Luke@luke_pighetti·
Iran? Kurdistan???
Euskara
2
0
5
2.2K
Milad Akarie
Milad Akarie@milad_akarie·
I just realized you can use null-aware elements in Dart maps too — not just iterables. It doesn’t look like it at first, but the key is completely omitted when the value is null. #Flutter #Dart #FlutterDev
Milad Akarie tweet media
English
5
6
45
2.1K
Rebaz Raouf
Rebaz Raouf@rebazdev·
Ever needed to embed some config, assets, or test data and just access it instantly at runtime without dealing with file loading? So we built EmbedMacro. Embeds files as byte arrays at compile time. Access them like regular files, but instant. @dart_lang @FlutterDev #macro_kit #embed
Rebaz Raouf tweet media
English
3
1
25
1.1K
Rebaz Raouf
Rebaz Raouf@rebazdev·
@nank1ro @FlutterDev @dart_lang I'm more inspired by the solidart framework itself 💙 than just the example. Your work inspired me to create widget_macro, and then I wanted to compare it with the existing example to see how they stack up against each other.
English
1
0
1
64
Rebaz Raouf
Rebaz Raouf@rebazdev·
I think there may be some confusion about what this package does. It's still a StatefulWidget. The key difference is that it removes the boilerplate of manually managing state. If you look at the generated code, you'll see all the standard lifecycle methods (initState, dispose, etc.) are still there. And just like always, you can override them whenever you need custom behavior. As stated in the README, this is intentionally a simple state management solution. It provides state, computed values, queries, side effects, and dependency injection. which covers the needs of most users. We're just getting started and may expand features based on feedback. I'd be happy to address specific gaps if you could clarify which concerns you have. The GitHub repo includes examples. As for benchmarks, I haven't created ones yet, but feel free to run your own tests. Since the package has zero dependencies and uses ValueNotifier under the hood, performance should be excellent.
English
1
0
1
41
Prince B
Prince B@optiflowx·
@rebazdev @FlutterDev @dart_lang When you come up with a solution that "removes boilerplate ", you must know your story and be in depth. Lifecycle of the models, memory, initialization and disposal, etc. How does it work if we no longer need initState/dispose etc methods. Be in-depth not vague. It's SM not UI.
English
3
0
0
57
Rebaz Raouf
Rebaz Raouf@rebazdev·
Thanks so much! Yeah, exactly it's all about spending your time on the actual problem you're solving instead of wrestling with boilerplate. The productivity boost is real when you can just focus on what matters and keep your code clean without all that repetitive state management ceremony. Plus macro kit is really fast
English
0
0
1
54
Rebaz Raouf
Rebaz Raouf@rebazdev·
Ready to eliminate Flutter boilerplate? 🚀 📦 Install: flutter pub add widget_macro 📖 Full docs: pub.dev/packages/widge… Try it and let me know what you think!
English
0
0
5
173
Rebaz Raouf
Rebaz Raouf@rebazdev·
🎨 Before vs After BEFORE: 50+ lines of boilerplate - initState, dispose - ValueNotifier setup - addListener, removeListener - setState calls everywhere AFTER: Just annotations @state, @Computed, @Query That's the power of macros.
English
1
0
1
152