3 ms·

This is an architecture preference disguised as a tool review. It should be called "Reasons why I don't like client-side web programming and prefer to work with

• charlysisto 12y ago
  The title and some of the critics are unfortunate but this post nevertheless is hitting a soft spot for me. I've been through backbone & angular and I'm starting to question the necessity of a full blown framework when all I want is some structured js for each page/resource. More fundamentally it seems the offer on js libraries are either tailored to eye-candy widgets or the big SPA. Nothing has popped in my radar as proposing an incremental step from server side HTML to MV([A–Z]) Dom/json manipulation which entices you to almost build the app twice. What I'd really like to see rather than a client-side-solution is a server/client migration path from html to spa without being tide to one or the other The links he included (see below) bring up the same concerns.... http://mir.aculo.us/2013/02/26/client-side-mvc-is-not-a-silver-bullet/ http://mir.aculo.us/2013/02/26/client-side-mvc-is-not-a-silv... http://www.shopify.com/technology/15646068-rebuilding-the-shopify-admin-improving-developer-productivity-by-deleting-28-000-lines-of-javascript http://www.shopify.com/technology/15646068-rebuilding-the-sh...