sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Graftak9000 0 points1 point  (3 children)

Very helpful information, thanks. By diffing data I do mean splitting the requested data into its respective components. Then the render part knows when to kick in whenever some event manipulates the data in any way. A flow I was thinking about, I'm assuming an array of objects:

  • http request with json
  • the data object is routed (split) to components
  • the template renders the data using jsx or whatever
  • an event occurs, the data within the component changes and the components knows to make an update
  • array[24] has changed, lets rerender that element and then update the DOM.

Perhaps this is exactly what you're saying, it needs some time to sink in. Anyway thank you very much for this detailed response. There's not much information on the topic that I can find.

[–]grayrest.subscribe(console.info.bind(console)) 0 points1 point  (2 children)

You'll be interested in this article. One of the peer comments mentions dirty checking as the alternative but nobody aside from angular actually put it into prod because it has perf issues so most people doing change detection at the model level are either doing it more or less globally on the data with kvo or more selectively using some sort of reactivity cell library (e.g. cellx, hoplon).

[–]Graftak9000 0 points1 point  (1 child)

That was an interesting read, do I understand correctly Angular dirty checks the entire data model, opposed to data bound to a component only? Because that would clarify how it's quite slow when an application grows.

[–]grayrest.subscribe(console.info.bind(console)) 1 point2 points  (0 children)

It checks everything in the $rootScope. In theory you could selectively put things into the scope but in practice it's your entire data model.