I no longer program in Flutter but when I did I use to use getX. It was simple and I never had trouble with performance. As a matter of fact at one time I was working on a custom text editor and I was updating values at 60 fps and getX was able to handle that without trouble. So I really have no idea what type of performance you would need that needs to handle updates faster than that. Most people who write articles about getX have never actually tried to use it in a real app. And most of the complaints are focused on some beef between getX and another developer, very early in its release cycle many years ago because heaven forbid the getX developer posted benchmarks against other packages. Something that was apparently worked out, I have never seen the getX developer posting about other packages since then. It takes 2 people to have an argument, so the people who tend to bring it up are simply taking one side over the other. Personally I think people are just missing out on an easy way to manage state. Frankly I could care less whether my app used build context or not if it works the way I intend and at the speed I need.