How Basecamp Next got to be so damn fast without using much client-side UI

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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.

[ Parent | on HN ]