Re:Client-side MVC is not a silver bullet
by ricardobeat on Monday February 25, 2013 @10:16PM
(#5283704)
That's the implementor's fault, and usually the result of loading two dozen scripts, blocking ads, external webfonts, share buttons and other crap. A framework like Backbone is very lightweight and fast if used correctly (typed from an ipad 1)
[ Parent
| on HN ]
Re:Client-side MVC is not a silver bullet
by eduardordm on Monday February 25, 2013 @10:26PM
(#5283749)
Conceded, backbone shouldn't add stress to any website. But if you put together angularJs: directives on external html rendered in a ng-repeat (50 items or so) you will have to put the MBP on a table because it gets really warm.
Re:Client-side MVC is not a silver bullet
by ahoyhere on Monday February 25, 2013 @10:31PM
(#5283763)
Rendering anything but the simplest DOM templates from JSON can be extremely slow. We so wrote a book on JavaScript performance -- runtime performance, not simply asset delivery. In that nearly 4yo book, we recommended against templating. A couple years later, we thought things got better & faster and it wasn't an issue any more. We thought wrong.
Re:Client-side MVC is not a silver bullet
by ricardobeat on Monday February 25, 2013 @11:11PM
(#5283899)
It is usually more than fast enough. The project I'm currently working on renders completely on the client with around ten different templates/partials, and the rendering adds up to just a couple ms - that's using handlebars which is not the fastest engine around. 99% of the application time is on data retrieval and processing.
I understand you had issues with your project, and email apps are complicated beasts, but let's not generalize. The truth is in between. I bet rendering a complex template server-side on Ruby can be slower than js.