sczerwin

4 ms·

1.
by sczerwin 13y ago
As much as we would love to speak to that, we've unfortunately haven't done this same type of benchmarking/analysis on backbone.js. This was our first foray into a Javascript MVC-ish frameworks. After doing the paper researc
2.
by sczerwin 13y ago
When we were doing the profiling while developing the optimizations, we were surprised to find that the Javascript thread was spending something like 50% of its time in the method to remove a DOM element. Now, maybe that's because Ang
3.
by sczerwin 13y ago
We didn't need a perfectly clean solution, just one that showed we could get the performance we desired while still following Angular's main tenets -- separate model from view, leave HTML generation to templates, testability, etc.
4.
by sczerwin 13y ago
The implementation of overriding the scope's $watch method is fairly straight forward. We gave our optimization directive a fairly high priority so that it was guaranteed to be run first (among all the other directives on an element).
5.
by sczerwin 13y ago
Yes, we actually didn't modify any of the AngularJS source itself, but just overrode methods and inserted ourselves where we needed to. For example, we override $scope.$watch to intercept watch registration. However, we do rely on so
6.
by sczerwin 13y ago
That's a very fair point and we have work to do to optimize our site for mobile viewing (I'm an engineer at Scalyr). One twist on the optimization that we could have used but didn't was trigger the tokenization on mousedown a