When to implement javascript MVC framework

Question

I work at a small web agency that specializes in web applications for startups. I am pushing my boss to put more resources into building robust frameworks on the client side using javascript mvc standards (I'm using BackboneJS) and templating (using underscore)

I'm realizing that there are some situations where robust javascript frameworks make sense (eg. complex one-page web applications), and others where it may not be worth the effort (a list of blog posts, which can be templated using php)

We are trying to develop a standard for when to implement a javascript framework on a page, and when to rely on php for templating and server requests.

I am hoping some folks on the interwebs community have some thoughts on this matter, or could reference me to articles on this topic. I have some ideas of my own, but an "expert opinion" would hold more sway with my management team...

Answer 1

You might want to take into consideration who the end users are. For Slower Devices (Office Desktops, 3 Year old Laptops etc.) a huge Clientside Framework can cause lacks and it might end up not being much fun to surf the page.

So if the website focuses on older people, non techies or office workers, you might want to take it easy on the javascript.