How to Evaluate Flutter Dependencies (or, why I won't use GetX)

When you're coding with GetX you're not doing a Flutter app... you're doing a GetX app. If something goes wrong or have issues, you depend on that library to maybe fix it... if you're moving to new projects (real ones) no one uses it and you'll be confused on how Flutter actually works. Update: This video explains GetX perfectly: [video TL;DR: Lack of documentation, lots of bugs, PR don't get much attention, every new features that touches core Widgets, GetX needs to re-implement (and poorly, looks like) them. GetX UI is QUESTIONABLE (doesn't follow any user interface guideline from Google or Apple), production Widgets have DEBUG Strings 💀and using custom Widgets breaks the minim…

This has been discussed many times and the reason why as well. You can read it from Experts, ex Googlers (who worked building Flutter), etc: https://twitter.com/scottstoll2017/status/1468431032240246784 [video https://twitter.com/filiphracek/status/1468565501701939203 TL;DR: Lack of documentation (you don't know what many methods or classes do). Lots of debug or during development code landing on production. Lack of unit testing (or barely any) to guarantee code quality or even the knowing that what it was develop, actually works as expected. Several poor architecture decisions and low code quality in general. Bad practices (mostly related in the use of BuildContext) and many more... y…

Here, watch this: link to this video