<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Some Random Dude &#187; conundrum</title>
	<atom:link href="http://www.somerandomdude.com/tag/conundrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.somerandomdude.com</link>
	<description>Some Random Dude is a blog by P.J. Onori that covers design &#38; technology in the broadest sense possible.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:37:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>To Advocate For or Abandon the 10%</title>
		<link>http://www.somerandomdude.com/2008/07/18/the-ten-percent/</link>
		<comments>http://www.somerandomdude.com/2008/07/18/the-ten-percent/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 17:57:51 +0000</pubDate>
		<dc:creator>P.J. Onori</dc:creator>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[conundrum]]></category>
		<category><![CDATA[internet-explorer]]></category>
		<category><![CDATA[traffic]]></category>
		<category><![CDATA[web-projects]]></category>

		<guid isPermaLink="false">http://www.somerandomdude.net/blog/opinion/the-ten-percent/</guid>
		<description><![CDATA[Back in 2002 or 2003, when Internet Explorer reigned at the undisputed leader in browser market share, I was very outspoken over the need to support all browsers &#8211; even those with only 5% share or less. I argued about the need to provide a consistent experience for all users, regardless of what browser or [...]]]></description>
			<content:encoded><![CDATA[<p>Back in 2002 or 2003, when Internet Explorer reigned at the undisputed leader in browser market share, I was very outspoken over the need to support all browsers &#8211; even those with only 5% share or less. I argued about the need to provide a consistent experience for all users, regardless of what browser or version they decide (or as forced) to use. This ideology was all the easier to adopt considering how had market share at the time &#8211; I feel as though my strong feelings were just as much about not idly allowing the &#8220;evil&#8221; corporate browser to swallow even more share by helping make it the de-facto browser on the internet. Fast forward 5+ years and oh, how the tables are turning. A new generation is jumping online and they&#8217;re not just blindly clicking the blue &#8216;e&#8217; on their desktop. Firefox 3 shattered the record for most downloads and, according to some metrics, is passing up <a href="http://news.cnet.com/8301-13505_3-9959427-16.html">20% global market share</a> and <a href="http://mozillalinks.org/wp/2008/01/firefox-global-market-share-reaches-211/">well above 40%</a> in some European countries. The underdog is now the up-and-comer.<br />
<span id="more-660"></span><br />
Which brings me to why I am writing this article. I am in the process of putting ideas and concepts together for the redesign of somerandomdude.net which has taken me down some very interesting paths. The problem is, many of these ideas are simply not going to work on older browsers &#8211; most notably, Internet Explorer 6. IE6 still comprises roughly 10% of the traffic on this site, which <em>should</em> be far too significant to ignore. Here is the conundrum &#8211; I just do not seem to care. IE6 is, by current standards, a train wreck of a browser. I have seen more web projects than I would like to remember use the majority of their production time just to resolve IE6 issues. Still, I fail to see the philosophical difference between supporting the Netscape 7&#8242;s in 2002 and the Internet Explorer 6&#8242;s in 2008. In fact, IE6 gets more share now than any of the browsers I fought to support did. All that said, I <em>still</em> am leaning towards not supporting it.</p>
<p>My argument towards not supporting IE6 for the new redesign would mean faster production time, and allow me to use publishing methods which would help me post <em>much</em> more frequently. So here&#8217;s the question &#8211; do ends justify the means or is this just an example of hypocrisy at its finest? My justification is continuing to support IE6 will limit what I can do to the blog (in the time I have to build it) in order to make posting easier &#8211; which <em>should</em> allow more content to be published. So, do I continue to give an equal experience to the 10% or give an improved experience to the 90%? This question is not new by any means, but I find myself on the other side of the argument this time.</p>
<p>What are your thoughts on this? Does creating a consistent experience trump a better site for the majority? Do the ends justify the means? Should a compromise be found?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.somerandomdude.com/2008/07/18/the-ten-percent/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>New Grassroots Campaign Aims to Save Some Developers</title>
		<link>http://www.somerandomdude.com/2008/03/25/save-the-developers/</link>
		<comments>http://www.somerandomdude.com/2008/03/25/save-the-developers/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 20:13:30 +0000</pubDate>
		<dc:creator>P.J. Onori</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[conundrum]]></category>
		<category><![CDATA[evangelist]]></category>
		<category><![CDATA[ie6]]></category>
		<category><![CDATA[internet-explorer-6]]></category>
		<category><![CDATA[organizers]]></category>
		<category><![CDATA[web-projects]]></category>

		<guid isPermaLink="false">http://www.somerandomdude.net/blog/development/save-the-developers/</guid>
		<description><![CDATA[As a former front-end developer, I know the horrors of building HTML/CSS sites that work across all browsers. Frankly, the whole cross-browser conundrum was one reason why I got out of it a year or two ago. While I may not get paid to build static websites anymore, I obviously am still vulnerable to these [...]]]></description>
			<content:encoded><![CDATA[<p>As a former front-end developer, I know the horrors of building HTML/CSS sites that work across all browsers. Frankly, the whole cross-browser conundrum was one reason why I got out of it a year or two ago. While I may not get paid to build static websites anymore, I obviously am still vulnerable to these problems with the sporadic interface/visual revamps I make to this blog and other minor web projects I take on. As the months go by, I see my ability to (reliably) develop HTML/CSS that will work in older browsers. That is why I really like the notion of what the <a href="http://www.savethedevelopers.org">Save the Developers</a> campaign is trying to do.</p>
<p>The idea is extremely basic &#8211; get owners of websites to put a small amount of Javascript on their sites that encourages Internet Explorer 6 users to upgrade to a more standards-friendly browser. The organizers of the project were smart not to make this some evangelist movement for their favorite browser; rather opting users to choose <em>any</em> modern browser that fits their needs, including the mixed-bag which is Internet Explorer 7. I have decided to participate not only to save the blood pressure of front-end web developers across the world, but for my sake as well. I am a sucker for grassroots campaigns as many of you may know by now. For those of you who are front-end developers yet less fascinated with this sort of thing, may I suggest that the sooner we can get users off of obsolete browsers, the better our (professional) lives will be.</p>
<p><strong><a href="http://www.savethedevelopers.org">www.savethedevelopers.org</a></strong></p>
]]></content:encoded>
			<wfw:commentRss>http://www.somerandomdude.com/2008/03/25/save-the-developers/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using apc (Feed is rejected)
Page Caching using apc
Database Caching 1/15 queries in 0.009 seconds using apc
Object Caching 300/337 objects using apc

Served from: www.somerandomdude.com @ 2012-02-09 17:47:34 -->
