There's just something about the location of this that has me concerned.

It's seems prayer is in due order.

Magnitude 6.4 - KERMADEC ISLANDS REGION

2006 March 31 13:21:03 UTC

* Details
* Maps

Where can I find...?
Earthquake Details
Magnitude 6.4 (Strong)
# Date-Time Friday, March 31, 2006 at 13:21:03 (UTC)
= Coordinated Universal Time
# Saturday, April 1, 2006 at 1:21:03 AM
= local time at epicenter
Location 29.468�S, 176.755�W
Depth 27.1 km (16.8 miles) set by location program
Region KERMADEC ISLANDS REGION
# Distances 110 km (69 miles) ESE (103�) from Raoul Island, Kermadec Islands
# 937 km (582 miles) S (189�) from NUKU'ALOFA, Tonga
# 3063 km (1903 miles) WSW (239�) from PAPEETE, Tahiti, French Polynesia
Location Uncertainty horizontal /- 10.2 km (6.3 miles); depth fixed by location program
Parameters Nst= 83, Nph= 83, Dmin=115.4 km, Rmss=1.11 sec, Gp= 61�,
M-type=moment magnitude (Mw), Version=6
# Source U.S. Geological Survey, National Earthquake Information Center
World Data Center for Seismology, Denver
Event ID uskyay

via a recent post to the IronPython's Community Interface, Dino Viehland writs:

We have just released IronPython 1.0 Beta 5. This release focuses primarily on improving IronPython’s performance. In this area we’ve reduced working set and startup type by optimizing methods on-demand, improved the speed of attribute access, reduced the overhead in many basic operations (e.g. equality checks and uninitialized checks for local variables), and done other various fine tuning. As usual there are also a good number of bug fixes (primarily focused on community reported bugs). There was also one significant API change in the .NET <-> Python interoperability area:

If we have the following definitions:

Premature Male-Pattern Baldness

Alex Bosworth's Weblog: Ajax and XSLT in Web Development

I especially like Google's choice to be agnostic about namespaces, as XML namespaces make me want to tear my hair out.

I tell ya... I was this >< close to taking this piece and dissecting it into billion little "Itsy-Bitsy, Teenie-Weenie, Here's A Phreakin' Clue For Freebie" pieces... (and there are about 15 places that, in fact, made me want to rip out my own hair! Just not for the same reasons. [hint: XML NAMESPACES ARE MIND NUMBINGLY EASY TO UNDERSTAND!!!]

That said, here's why I chose not to:

In addition to that legal requirement, there are some strong recommendations that aren't legally required. You should make it clear to your users that you are using Swish-e in your product by listing Swish-e in your documentation and, if you have a web site, with an easy to find link on your web site. (Consider using the Swish-e logo). You must feel guilt if you add features or bug fixes to the software and do not inform other users of swish-e via the Swish-e discussion list, and you should think about buying the developers a beer. Or two. Or until they say 'stop'.

Smile :)

Rory says a lot of what I would have said in criticism of the passion post I found via Mini-Microsoft and does it with a lot less bitterness than I could ever muster. If you ask me, Microsoft could do with a lot less of its so-called passionate employees.

I like this post from Dare (in fact, it seems to me that Dare's been on quite the roll lately)

If there is one thing in life I have been accused of most often (and I've been accused of a LOT of things ;) its being passionate.

I've always taken this as a compliment, although its not always meant as one.

Not my problem.

What is my problem?

And when that man is Tim Bray and the person he is inferring his trust works for Microsoft... Well my friends, Tim Bray has just proven once again why I admire him as much as I do:

(which I’ve never quite managed to understand, but Don Box says it’s at the center of WS-everything, and I trust Don)

Wow!

Okay, so the person he's inferring his trust upon is Don Box. Pretty safe bet if you're in the market to infer trust upon someone.

But did I mention Don Box works for Microsoft?

That should be plenty there, so I'll just leave it as-is.

Jonathan Robie's XQuery Blog XQuery, XQJ, Data Integration, XML, Databases, and the Web.

So I knew Jonathan Robie (fifth name down... yeah, in case you were unaware, Jonathan kinda knows a thing or two about XQuery ;)) had started a blog a while back. But it seems he has gone from his once in a blue moon post's to once every day or two.

SUBSCRIBED! :)

So no one gets fired for Google-like systems architecture. No. Outside the crescendoing Web 2.0 bubble, no one gets hired in the first place if there's the slightest sniff they'd contemplate such a thing. Shame. Web 2.0 is not a bubble (square-one-dot-com) because it's based on near-trivial technology. It's a bubble because there are very few opportunities for arbitrage in a marketplace whose point is to provide customers unprecedented transparency and choice. The very place where such an approach can more consistently provide value is within the enterprise whose information systems have so long been bantustans of baroque and isolated systems. The enterprise is where there is a real chance of information systems revolution from Google-like technology. And it's the one place where no one is looking to build and deploy technology the way Google does.

Yet Another Fantastic Post from Uche. I could not agree more with ALL of this.

Two things to point out:

Line 6: This is a Google-Reader-specific extension of some sort, and I have no idea what it means, and that’s just fine. Atom requires that software tolerate this kind of thing, which is why we’ll probably never need Atom 2.0 or even 1.0.0.0.1.

You'd have to be somewhat of a fanatical follower of the RSS "babys-mama-drama" to understand why this has me rolling my a$$ around my office floor in convulsive laughter.

Keep em' coming Tim! I need a good laugh and a smile like this every two to three hours such that I can remember why I love this business as much as I do :)

...and we lost. We lost the battle, our desire to change, adapt, create, and be free from ANYTHING that might suggest we live within the confines of someone elses standards.

Folks will increasingly stop creating new XML-based languages at the front-end. Instead, the XML-based semantics will be tunnelled into a small set of existing vocabularies, most notably XHTML, RSS/Atom and ODF.

I'm sorry, but I could not disagree more with EVERYTHING in the above statement.

Oh wait... firstly, I guess I should preface this with the fact that there is another preview version of IE7 available, cleverly labeled:

Internet Explorer 7 Beta 2 Preview - released on March 20th

This would, of course, be in replacement for:

Internet Explorer 7 Beta 2 Preview - not released on March 20th

Of course never wanting to confuse things even further, here's a sample "clarification" follow-up comment to yesterdays announcement:

Beta 2 isn't even out yet and we have a final release later.

So, in other words,

This is not Beta 2, but the second preview release thats leading up to Beta 2, which is labeled "Internet Explorer 7 Beta 2 Preview - released on March 20th" which SHOULD NOT be confused with "Internet Explorer 7 Beta 2 Preview - not released on March 20th" (and really, how could it be???!!! ;) which will eventually be replaced by Beta 2, to then be followed up with a "final release later."

Q: "final release later."? Does that refer to a final Final release, or a final Beta 2 release?

You know what... Nevermind... I don't want to know.

Okay then.... So, now that we have that all cleared up lets first look at what the Acid 2 test results should look like:

Dare Obasanjo aka Carnage4Life - Instant Messaging Networks vs. Public Social Networks

Of course, nothing stops the recruiter from just blogging about our relationship or creating a blogroll of "people I'm trying to poach from Microsoft" but that's just her word against mine. With publicly exposing her social network, it is now confirmed that we have some sort of relationship. That's not what I agreed to when I accepted her as an IM contact.

A lot of this is gut feel from a lot of us who use and build these products. However I'd rather err on the conservative side than piss off our users in a crass attempt to increase the usage of one of our features.

Whether this scenario, or any other, the fact that I might have someone on my IM "buddy" list *SHOULD NOT* infer any rights upon that person (who would in turn have me on their contact list) to make this information public in *ANY WAY*.

By forcing me to explicity allow someone to add me to their social network, whether public, semi-public, semi-private, or private, puts that control into MY hands, not theirs. With this in mind the following quote:

Maria had a tough go of it in life. Today, it seems she decided enough was enough, ingesting weed killer, bringing an end to the pain and suffering of living a life in which Schizophrenia had taken control.

I never knew Maria. But she will never be forgotten.

The Sudoku solving stylesheet craze has been catching on...

Dimitre Novatchev, creator of FXSL and xsl-list regular, has written a stylesheet (in typical Dimitre style) which attacks the problem from a slightly different angle.

It seems while I wasn't paying attention, Andrew Welch up'd and started a blog.

Welcome Andrew! Subscribed.

Regarding Andrew's post.... I have some more to announce regarding the mentioned Sudoku craze. Hopefully announce that later today.

In the mean time, pay a visit to Andrew's blog and learn a thing or two you didn't already know :)