From b6d929c019f0d5022c8c34b63fdb2a9be079cf00 Mon Sep 17 00:00:00 2001 From: Addy Osmani Date: Sat, 11 May 2013 19:18:36 +0100 Subject: [PATCH] For #453 - adds initial angular-perf readme. --- architecture-examples/angularjs-perf/readme.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 architecture-examples/angularjs-perf/readme.md diff --git a/architecture-examples/angularjs-perf/readme.md b/architecture-examples/angularjs-perf/readme.md new file mode 100644 index 0000000000..a554a323d8 --- /dev/null +++ b/architecture-examples/angularjs-perf/readme.md @@ -0,0 +1,5 @@ +# AngularJS (performance optimized) TodoMVC app + +The normal AngularJS TodoMVC implemetation performs deep watching of the todos array object. This means that it keeps an in-memory copy of the complete array that is used for dirty checking in order to detect model mutations. For smaller applications such as TodoMVC, this is completely fine as one trades off a little memory and performance for the sake of simplicity. + +In larger more complex applications however, where one might be working with 100s or 1000s of large objects one definitely should avoid using this approach. This implementation of the AngularJS app demonstrates the correct way to approach this problem when working in larger apps.