3 ms·
I was surprised to find that Angular has a limited duration time window during which changes will update the view. In my case, symptoms were observed only afte
by zxv 10y ago
I was surprised to find that Angular has a limited duration time window during which changes will update the view. In my case, symptoms were observed only after deployment, for user who had a high latency connection between their browser and the server.
One could mitigate this by calling $scope.$apply() after every change. But if you have to apply() all changes, then what's the point of having angular handle synchronization?
- zkhalique 10y agoIn our platform, we just let the developer call a function manually after updating the state of a tool. So it is event-driven reactive changes. Yes, shockingly, we don't save those keystrokes, but we also don't have the elaborate dirty checking. The developer of a component is extremely likely to make sure during development that the update to a state has updated the view. Of course, you could just hook up React or VDOM or mirthril and it's totally complementary to what we do.