<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Total Control Demo! &#8211; The Content Management System for Law Firms</title>
	<atom:link href="http://www.paperstreet.com/blog/2123/feed" rel="self" type="application/rss+xml" />
	<link>http://www.paperstreet.com/blog/2123</link>
	<description>Law Firm Internet Marketing Blog, Web Design Articles</description>
	<lastBuildDate>Thu, 19 Jan 2012 22:45:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Kyle Aikens</title>
		<link>http://www.paperstreet.com/blog/2123/comment-page-1#comment-99670</link>
		<dc:creator>Kyle Aikens</dc:creator>
		<pubDate>Fri, 05 Mar 2010 17:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.paperstreet.com/blog/?p=2123#comment-99670</guid>
		<description>Personally I really don&#8217;t have little issues with IE6 these days... As a developer i&#039;ve adapted to combining Standards with IE6 Support. I&#8217;ve gotten to a point where I know what&#8217;s not going to conflict and what is going to 
 
I do however entirely disagree with the fact that nothing is going to change.  I think we&#8217;ll see a huge drop in numbers over the next few months.  A huge majority of IE6 users are based around corporate intranets, and if corporate offices can&#8217;t use Google docs or YouTube?  That&#8217;s just crazy. 
 
I think when people see a huge red box on Google (the most trusted website in the world) that instructs you to upgrade your browser.  It&#8217;ll happen.  I think a majority of people just don&#8217;t know any better,  this will be a much needed shove in the right direction.   
 
We&#8217;ll see, is a good stance.  But I think when we decide its time, we should drop it all together. A majority of build time that happens to correct IE6 issues happens during the build process before IE6 is even looked at.  Josh, Ariel, and I know we&#8217;re going to have to take an extra 30 minutes to make a certain element use all gif instead of pngs, or know that we have to put padding on floated elements and not margins.  All of these precautions can be thrown out the window, and we can build in a more modern and quicker way geared towards Standards Based browsers only. 
 
Not to mention beta IE9 with HTML5, CSS3, and W3C Standards is coming out this month&#8230; Every major browser will now support CSS3 and HTML5. Horrah! 
 
Although PaperStreet may have 4.6% of IE6 users, the world still has a massive 17-20% market share. Statistically its gone down about 9-10% per year.  So in December we&#8217;re looking at less than 10% of the world, if not more due to these giants dropping support.   
 </description>
		<content:encoded><![CDATA[<p>Personally I really don&rsquo;t have little issues with IE6 these days&#8230; As a developer i&#039;ve adapted to combining Standards with IE6 Support. I&rsquo;ve gotten to a point where I know what&rsquo;s not going to conflict and what is going to </p>
<p>I do however entirely disagree with the fact that nothing is going to change.  I think we&rsquo;ll see a huge drop in numbers over the next few months.  A huge majority of IE6 users are based around corporate intranets, and if corporate offices can&rsquo;t use Google docs or YouTube?  That&rsquo;s just crazy. </p>
<p>I think when people see a huge red box on Google (the most trusted website in the world) that instructs you to upgrade your browser.  It&rsquo;ll happen.  I think a majority of people just don&rsquo;t know any better,  this will be a much needed shove in the right direction.   </p>
<p>We&rsquo;ll see, is a good stance.  But I think when we decide its time, we should drop it all together. A majority of build time that happens to correct IE6 issues happens during the build process before IE6 is even looked at.  Josh, Ariel, and I know we&rsquo;re going to have to take an extra 30 minutes to make a certain element use all gif instead of pngs, or know that we have to put padding on floated elements and not margins.  All of these precautions can be thrown out the window, and we can build in a more modern and quicker way geared towards Standards Based browsers only. </p>
<p>Not to mention beta IE9 with HTML5, CSS3, and W3C Standards is coming out this month&hellip; Every major browser will now support CSS3 and HTML5. Horrah! </p>
<p>Although PaperStreet may have 4.6% of IE6 users, the world still has a massive 17-20% market share. Statistically its gone down about 9-10% per year.  So in December we&rsquo;re looking at less than 10% of the world, if not more due to these giants dropping support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

