In this case, it isn't actually Angular. The delay is actually related to one of two things (I've profiled pretty heavily) 1. When moving between cards (in th

In this case, it isn't actually Angular. The delay is actually related to one of two things (I've profiled pretty heavily) 1. When moving between cards (in the card view), the render is very expensive. The code runs in about 50ms, which could be faster, but is good enough to feel responsive if rendering were not an issue. 2. When searching, laying out the grid is, again, very expensive to render. I've cut out Angular from all except for event handling. The grid items themselves are read-only bound (although the collection watch still exists), and I rearrange their position/visibility through CSS. This is, in my opinion, not a fault of Angular's. The other frameworks wouldn't fair too much better.