Re:How Basecamp Next got to be so damn fast without using mu...
by jonknee on Friday February 17, 2012 @11:31AM
(#3603885)
That's nonsense, the same issue would apply on the server side templates. If you go around messing with DIVs without an idea of the consequences, you will get in trouble regardless of your templates being on the server or client. If you try to have the designer do a redesign without testing the application afterwards, you're always in for trouble.
Re:How Basecamp Next got to be so damn fast without using mu...
by zaidf on Friday February 17, 2012 @01:06PM
(#3604292)
you will get in trouble regardless of your templates being on the server or client
My view is that you will get in significantly less trouble because manipulating an HTML template that is rendered on server side is much easier to manage and adapt to a new design than finding nitpick jquery selectors across the app that depend on a specific div structure.
Btw, my post doesn't imply anywhere that a designer should redesign an app without testing. Therefore, your argument about testing is garbage.
Re:How Basecamp Next got to be so damn fast without using mu...
by agilebyte on Friday February 17, 2012 @05:55PM
(#3605305)
Rather than "finding nitpick jquery selectors" I use a client side framework (backbone.js) with a lot of Views which makes my development faster vs using server side templating, so I cannot share your opinion.
For example, if you are populating a bunch of divs inside a parent div with the data returned using json, you would describe this using something like jquery selectors. Now if someone else comes and moves around the div during a redesign, he must go through whole bunch of js to make sure his shuffling of the divs around won't break the jquery selectors populating the data from json.
Now think about having a parent div that is simply populated with returned HTML from server-side and it seems way easier than using json to populate the data.