<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Debugging and Profiling JavaScript</title>
	<link>http://codeblog.palos.ro/2007/05/05/debugging-and-profiling-javascript/</link>
	<description>Thoughts about high architecture and sheer speed.</description>
	<pubDate>Sat, 19 May 2012 22:11:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: Stephane Grenier</title>
		<link>http://codeblog.palos.ro/2007/05/05/debugging-and-profiling-javascript/#comment-255</link>
		<author>Stephane Grenier</author>
		<pubDate>Fri, 18 Jan 2008 19:32:15 +0000</pubDate>
		<guid>http://codeblog.palos.ro/2007/05/05/debugging-and-profiling-javascript/#comment-255</guid>
					<description>I couldn't agree more. I've got an application that works in FireFox but won't in IE. Without tools like Firebug it's brutally hard to determine the cause. Most of the IE debugging tools really lack in comparison and make the job very painful. 

This makes me think that unless things change, most web developer (AJAX especially) will build for FF and support IE afterwards. This means that IE will continue to lose market share unless they can address this issue.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more. I&#8217;ve got an application that works in FireFox but won&#8217;t in IE. Without tools like Firebug it&#8217;s brutally hard to determine the cause. Most of the IE debugging tools really lack in comparison and make the job very painful. </p>
<p>This makes me think that unless things change, most web developer (AJAX especially) will build for FF and support IE afterwards. This means that IE will continue to lose market share unless they can address this issue.</p>
]]></content:encoded>
				</item>
</channel>
</rss>

