> This "dirty checking" can quickly lead to pathological performance issues. I would say that "dirty checking" is a better approach. The code is cleaner and wi

> This "dirty checking" can quickly lead to pathological performance issues. I would say that "dirty checking" is a better approach. The code is cleaner and with Object.observe() there are no performance issues even in _edge cases_ with thousands of monitored objects.