getx is all in one for single Developer .no need to maintaintain any state just use reactive variable to see changes..you are not going to make any game so no need to maintain state.. another is it is also possible to make big application with getx...rather bloc or other is difficult for making big application
GetX is the worst flutter state manager because it has a high coupling index and forces the programmer to only use its components, which are often not as good as native flutter or any other package :)
@@mago.regulo the getx controller is divided to only use the functions and dependencies according to what is needed, that you got used to using a state manager and you no longer want to learn another one will be your problem
@@ALEXCODE971 How can you say that it is divided if 100% of your screens will be forced to extend the getx state. Furthermore, it has been months without updates and upgrades.
Hmm, so you update app state using setState() ? Performance wise, setState is not as optimised as any state management package mentioned in the video. Feel free to try out them !
What would you do if you wanna update a screen state from another sceeen? You can do nothing but pass the function required to update the state from the screen to the other one, and when you will have multiple screens yiu have to pass the function into that complex network of screens , and that sucks
i think bloc should be considered as a design pattern but not state management tool. Because bloc is depending on provider package too
Good insight !
getx is all in one for single Developer .no need to maintaintain any state just use reactive variable to see changes..you are not going to make any game so no need to maintain state..
another is it is also possible to make big application with getx...rather bloc or other is difficult for making big application
Great insight !
GetX is the worst flutter state manager because it has a high coupling index and forces the programmer to only use its components, which are often not as good as native flutter or any other package :)
It is also dangerous to have an application that depends 100% on just one package.
@@mago.regulo the getx controller is divided to only use the functions and dependencies according to what is needed, that you got used to using a state manager and you no longer want to learn another one will be your problem
@@ALEXCODE971 How can you say that it is divided if 100% of your screens will be forced to extend the getx state. Furthermore, it has been months without updates and upgrades.
Which one work for flutter web
Hi, all of them works for flutter web depends on the project complexity.
Provider indeed
Good choice 👍
GetX for the win!! ❤
❤️
Yes sir ji ❤❤
i am without using any statemanagement in flutter
Hmm, so you update app state using setState() ? Performance wise, setState is not as optimised as any state management package mentioned in the video. Feel free to try out them !
What would you do if you wanna update a screen state from another sceeen?
You can do nothing but pass the function required to update the state from the screen to the other one, and when you will have multiple screens yiu have to pass the function into that complex network of screens , and that sucks
definitely provider
Great choice !
In dis video?
You have any other options aside from these four ?
👍👍👍👍
🙏🙏🙏🙏
First comment
✅
play x2
Minglished
rude