Third party scripts/content
With the ever increasing use of third party calls off site one runs across days when site struggles to finish loading - something I hate.
Case in point today gravatar.com is acting up and two sites I'm currently jumping back and fourth between are failing to finish loading one on a couple of script/content calls. Ok it's not a huge issue as largely the sites do function despite this but at times these unresolving calls can cause dynamic content to fail to load, depending I guess at which stage things start to struggle.
A death knell sounds?
? It certainly feels that way, or am I just in a state of moribund depression over the whole nature of web development and Standards?
Geocities RIP
The end of another of those little eras in the life of the internet.
Geocities has been around as long as I can remember, well quite long.
They shall be missed - erm well maybe not but na speak ill of the dead!
Many of us probably cut our web creation/hosting teeth on this service, it was one of the first web hosts, it feels strangely odd that it's gone.
It's funny how such a large organization can manage to make such a balls up of a takeover 
Browsers - the bain of our lives?
So Chrome 3 is in Beta, wonderful, and how RAD of them!
They are reported to be making a concerted effort to support HTML5; is this a good thing?
Am I suddenly to start making use of HTML5 seeing as how one browser out of many will support my efforts?
Of Tag Soup and Standards
I wonder and muse on whether, in reality, It was wise to give browsers the ability to render markup using the 'Tag Soup' rendering engine? or at least such a good ability.
Of course we know that without it more than half the web would vanish overnight, but I am constantly staggered by quite how effective it is at rendering code that is so completely wrong, code that you just stare at and honestly question how or why it has any right being parsed.
I further muse whether it may have been somehow! better to have had a mechanism by which if one wanted to make use of the power and flexibility and benefits derived from Standards and CSS that perhaps this should perhaps have been a function provided through the strict use of 'Strict DTD's only and that in using these the Tag Soup engine would be asked to be far less lenient with code parsing and rendering, thus clearly de-marking a line between good code and bad; I know that true XHTML provides for this and also that the XMl parser has been criticized for being far too strict and non fault tolerant, but I can only see that as a good thing , it says you Must write proper code or else we will return a page list of your errors, not that great a hardship or impossible goal to reach.
