<?xml version="1.0"?><rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	>
	<channel>
	<title>iain-simpson.org</title>
	<link>http://iain-simpson.org/</link>
	<description>iain-simpson.org</description>
	<language>en-gb</language>
	<copyright>Copyright 2008, Iain Simpson</copyright>
	<pubDate>Mon, 23 Jun 2008 03:57:01 -0700</pubDate>
	<lastBuildDate>Mon, 23 Jun 2008 03:59:44 -0700</lastBuildDate>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<generator>iainblog/1.0</generator>
	<webMaster>rss@iain-simpson.org</webMaster>
			<item>
			<title>Scattercode</title>
			<link>http://iain-simpson.org/post/73/	</link>
			<description><![CDATA[
			 &lt;Iain&gt; if it's not been coined already, i'm going to coin: SCATTERCODE &lt;Iain&gt; a php (or]]></description>
			<pubDate>Mon, 23 Jun 2008 03:57:01 -0700</pubDate>
			<guid isPermaLink="false">http://iain-simpson.org/post/73/</guid>
			<content:encoded><![CDATA[
			<p> &lt;Iain&gt; if it's not been coined already, i'm going to coin: SCATTERCODE<br /> &lt;Iain&gt; a php (or similar) project that pulls in includes from multiple levels of indirectly referenced files, which may, or may not be dynamically generated<br /> &lt;Iain&gt; for maximum effect, the location of any database tables used should be masked, so that it takes 45 mins to trace back through the awful mess, just to verify that the system is doing what you suspect </p> <p>You saw it here first! </p> 			
]]></content:encoded>
		</item>
			<item>
			<title>Holy. Shit.</title>
			<link>http://iain-simpson.org/post/72/	</link>
			<description><![CDATA[
			 This should require no introduction:  ]]></description>
			<pubDate>Sat, 29 Mar 2008 13:11:08 -0700</pubDate>
			<guid isPermaLink="false">http://iain-simpson.org/post/72/</guid>
			<content:encoded><![CDATA[
			 <p>This should require no introduction:</p> <p><a href="http://www.speedtest.net"><img border="0" src="http://www.speedtest.net/result/252621820.png" /></a></p> 			
]]></content:encoded>
		</item>
			<item>
			<title>Dynamicisificationing</title>
			<link>http://iain-simpson.org/post/71/	</link>
			<description><![CDATA[
			   Dynamicisificationing - the process of modifying an application or web page to replace a previous]]></description>
			<pubDate>Thu, 18 Oct 2007 13:22:30 -0700</pubDate>
			<guid isPermaLink="false">http://iain-simpson.org/post/71/</guid>
			<content:encoded><![CDATA[
			   <p><a href="http://www.googlemark.org?id=CHECK&amp;q=Dynamicisificationing">Dynamicisificationing<img border="0" src="http://www.googlemark.org/img/gm_10.gif" alt="(G)" title="Googlemarked!" style="display: inline" /></a> - the process of modifying an application or web page to replace a previously hardcoded element with a dynamically generated element.</p>     <p>You saw it here first! </p>   			
]]></content:encoded>
		</item>
			<item>
			<title>Safari for Windows!</title>
			<link>http://iain-simpson.org/post/70/	</link>
			<description><![CDATA[
			  Yay! I was reading BBC News, and saw that Apple have released a beta of Safari 3 for Mac OS and Wi]]></description>
			<pubDate>Mon, 11 Jun 2007 16:36:24 -0700</pubDate>
			<guid isPermaLink="false">http://iain-simpson.org/post/70/</guid>
			<content:encoded><![CDATA[
			  <p>Yay! I was reading BBC News, and saw that <a href="http://news.bbc.co.uk/1/hi/technology/6742439.stm" title="Apple announces Windows browser" onclick="window.open(this.href); return false;">Apple have released a beta of Safari 3 for Mac OS and Windows</a>.</p>   <p>Naturally, I hopped over to the Apple site to download it, and was bleeding from the eyes within minutes.</p>   <p>One thing that I've noticed about Macs, is that whenever I'm using one I feel as though my eyes are about to explode from the pressure of attempting to focus on the seemingly intentional blur effect applied to text. This is probably a personal thing, but I don't want to go back to the bad old days of dodgy CRT monitors that required manual focusing to avoid brain haemorrhage after prolonged exposure. I don't like the default softening effect that Macs apply to everything. Annoyingly, Safari on Windows applies it to all text rendered. Perhaps more annoyingly, there is no way to turn it off, meaning that I'm stuck with a multicoloured haze around characters, and the feeling that everything is in bold type.</p>   <p>Another problem I have is that Safari on Windows looks virtually identical to Safari on a Mac. Might be nice if you spend all day masturbating over Apple's latest product line, but very annoying if you like your UIs to be vaguely consistent. If you really want a Mac, you'll probably buy one anyway. Mac software should look like Mac software, Windows software should look like Windows software, and Linux software should look like whichever of the 101 or so widget sets that the developers decided to use.<br />  </p>   <p>Apple aren't the only offender here, but they're more relevant than Sony and the shitty custom apps they bundle with their PCs, or Nero with their increasingly shit &quot;Media Center Solution&quot; or whatever - what happened to Nero Burning Rom? - I couldn't find it on their site a few weeks back, and it looks like they only offer bundles of software that happen to have the ability to burn optical media.</p>   <p>I imagine that Apple try so hard to keep their Windows software looking like Mac software, is to get people used to the look and feel, and convert them to the way of the Mac. I still think that it's bad manners to ignore the look and feel of the system that your software is running on.</p>   <p>Unfortunately, I think Safari for Windows will be relegated to a place alongside Quicktime and iTunes, as software that I'll probably not use unless I have a file or site that won't work in anything else.<br />  </p>  			
]]></content:encoded>
		</item>
			<item>
			<title>Goodbye to an Old Friend</title>
			<link>http://iain-simpson.org/post/69/	</link>
			<description><![CDATA[
			  It had been threatening to pack in for a while, but one of my treasured 17&quot; DELL CRTs finally]]></description>
			<pubDate>Mon, 26 Feb 2007 15:54:01 -0800</pubDate>
			<guid isPermaLink="false">http://iain-simpson.org/post/69/</guid>
			<content:encoded><![CDATA[
			  <p>It had been threatening to pack in for a while, but one of my treasured 17&quot; DELL CRTs finally decided that enough was enough, and went off to silicon heaven. It had a good run, considering that it cost me &pound;20 from eBay at least 2 and a half years ago - though the P&amp;P wouldn't have been much less than that again.<br />  </p>   <p>So finally (probably to much jubilation and mockery of my insistence on using CRTs for so long), I've finally purchased a TFT monitor, and will soon have more permanent desk space available for coffee cups and assorted clutter. The unit in question is an <a href="http://www.dabs.com/productview.aspx?Quicklinx=4B5M" onclick="window.open(this.href); return false;">Iiyama 17&quot; LCD 1280 X 1024 Black 2ms</a>. It looks rather nice, and I'm hoping that the 2ms response time will go some way towards changing my opinions on cheap TFT screens. I've always said that I couldn't afford to replace my CRTs with a TFT that could match the image quality and response time. I hope I was wrong. I'm used to the 20.1&quot; Sony TFTs we use at work, and I'm probably spoiled slightly - those things go for around &pound;500 these days, whereas the Iiyama above is less than &pound;150.</p>   <p>Incidentally, I was reminded of some discount vouchers that Dabs emailed a while back, offering &pound;10 off an order over &pound;100 placed by 28/2/07. A fortunate discovery indeed, I thought. Perhaps my late display unit remembered that email, and chose its time to go accordingly. Or perhaps it was just 10 years old.</p>   <p>The identical unit that I'm using at the moment was manufactured at the same time, but seems to have seen less use, and is still very bright without cranking the brightness beyond 60%. Hopeully I'll manage to preserve this piece of computing history until it's 20 - by that point it'll probably be illegal to own, and impossible to dispose of.<br />  </p>  			
]]></content:encoded>
		</item>
		</channel>
</rss>