A nail in the technology coffin?

Something to consider:
In the UK, early evidence of large scale nail making comes from Roman times 2000 years ago.

To think the humble nail held its own for so long. However, had the blacksmiths of the day had a better marketing team perhaps we could have done away with the trusty iron technology of the day and perhaps moved on to I don't know ... wooden ones? They wouldn't have done the job as well, but they would have been cheaper to make. 

I think there would have been some backlash (or some lashed backs) when the Roman forts started falling down.

But now we have moved on from those historic days. All the marketing gurus have to say is "End of life..", and it is so, and everyone starts rebuilding forts with cheaper nails..

If I am being a bit vague, a case in point is the poor guy who rewrote his Foxpro application in Silverlight. That application would have continued to run for years under VFP. 

There are compelling reasons to move with new technology, but, because you were told to, is not one of them.

Now the screw, that was an innovation! But it didn't appear until the 15th century. So if my counting serves me correctly the nail held its domination for 6-700 years

So remember that the next time you get nailed by a technology company, wait for an innovative technology to appear and then say screw you.

Simple intro to using Python with IIS

Create an application
Add a script map
Request Path: *.py
Executable: C:\Python25\Python.exe %s %s
Name: Python

Add a file to the directory call it test.py
print
print 'Status: 200 OK'
print 'Content-type: text/html'
print
print ''
print ''
print '

This is a header

'
print '
' #this is a comment
print 'See this is just like most other HTML'
print '
'
print ''

Navigate to http://localhost/myWeb/test.py

Query strings and other HTTP parameters can be accessed through:
method = os.environ["REQUEST_METHOD"]
if method == "GET":
query = cgi.FieldStorage()
coName = query.getvalue("co")

AngularJS and IE 8

I need to support IE within desktop applications and MS sent XML data islands to the grave. XML data islands were an undervalued technology, particularly for databinding. Data islands are supported in later versions of IE through a backwards compatibility mode but that doesn't help with Chrome.

So naturally the gap gets filled and while there are many contenders it looks like AngularJS is the overall winner because you get so much out of the box. Why MS couldn't have done something similar is beyond me.
So AngularJS can run in IE and Chrome, but there's a catch. The following runs in Chrome but not in IE.

After lots of searching I found that you need this:

at the top of the HTML. It occurs when you are using AngularJS with Strict Contextual Escaping (SCE) mode enabled (the default) on IE8 or lower in quirks mode.