http://www.pathf.com/blogs/2007/09/parsing-html-wi/ Running commentary about agile development, user experience design and Ajax. Mon, 01 Dec 2008 23:04:40 +0000 http://wordpress.org/?v=2.5.1 http://www.pathf.com/blogs/2007/09/parsing-html-wi/#comment-348 Jan Wed, 12 Sep 2007 10:08:36 +0000 http://www.pathf.com/blogs/?p=255#comment-348 <p>A very good reason for using innerHTML is that it avoids duplicate code.<br /> You already know how to render data to a table on the server side.<br /> Implementing this a second time, in javascript, on the client side and keeping both implementations in sync blows up your codebase unnecessarily, is tedious and error-prone.</p> A very good reason for using innerHTML is that it avoids duplicate code.
You already know how to render data to a table on the server side.
Implementing this a second time, in javascript, on the client side and keeping both implementations in sync blows up your codebase unnecessarily, is tedious and error-prone.

]]> http://www.pathf.com/blogs/2007/09/parsing-html-wi/#comment-347 Anonymous Mon, 10 Sep 2007 23:35:28 +0000 http://www.pathf.com/blogs/?p=255#comment-347 <p>Another reason to use innerHTML is because it's so much faster. I have a case where I use ajax to paginate a table's content (thousands of rows, so it calls back to the server); Building the table manually with the DOM is very unwieldy and slow, the easier and faster solution is just to return back an updated TABLE element and toss that in with innerHTML.<br /> A browser's parsing engine is generally going to be much much faster than its javascript engine.<br /> The end-user doesn't care about coding niceness, only about perceived speed of the site.<br /> Building a TABLE on the server side is also much easier than trying to build one in the DOM.</p> Another reason to use innerHTML is because it’s so much faster. I have a case where I use ajax to paginate a table’s content (thousands of rows, so it calls back to the server); Building the table manually with the DOM is very unwieldy and slow, the easier and faster solution is just to return back an updated TABLE element and toss that in with innerHTML.
A browser’s parsing engine is generally going to be much much faster than its javascript engine.
The end-user doesn’t care about coding niceness, only about perceived speed of the site.
Building a TABLE on the server side is also much easier than trying to build one in the DOM.

]]>