Rob Eberhardt

It took ages, but I'm on dasBlog now.  Good riddance to dotText!  -- I bid it lovingly, though, since it served well for a 1st generation blog engine -- Somehow a couple hundred legitimate posts + comments garnered many thousands of comment spams.  I expect dasBlog will handle that all better; captchas are a tad annoying but effective, I hear.

That dasBlog is still under active development is a good sign.  I find that quality much more  important these days.  For reference, dotText was last updated almost 2yrs ago (and wasn't even really released).

So in other news (in the sense that no news is its own news), I haven't posted much of anything in a couple months, and even then there wasn't much meat.  I plan to start writing/posting with something like BlogJet.  (Yes, I actually used dotText's web-based editor, which was text-only in Firefox -- I'm entirely too comfortable with code for my own good).  Hopefully this ease will lubricate the writing process.

Regarding the transition: I used two great tools.  One was Aaron Junod's great dotText to dasBlog converter to migrate the content.  This would have done the trick many moons ago, except that I didn't want to orphan all my incoming links (a big no-no to a web dev like me).  Fortunately, Scott Hanselman published a Regex to remap URLs from dotText's format to dasBlog's (If only I hadn't fat-fingered that one the first time I tried it way back, it'd actually have worked). 

Finally, some outstanding meta-throbs junk:

1. Comments were probably lost.  Sorry.  I noticed spammers were usually changing the subject from the default "re: whatever", so I killed most of the rest. 
   
2. Search is gone for the moment.  I'll add it back in Real Soon Now.
3. Images and other locally-hosted junk is probably all broken.  I'll fix that slightly sooner.
4. Comments are screwy (dotText saved as HTML.  dasBlog doesn't.)
5. Layout is messed in IE6.
   

I add a custom IIF function to every VBscript I make:

' IIF recreated for VBscript
FUNCTION IIF(Expression, Truepart, Falsepart)
	IF Expression THEN 
		IIF = Truepart
	ELSE
		IIF = Falsepart
	END IF
END FUNCTION

'used like so:
strFlavor = IIF(strColor="brown", "chocolate", "not chocolate")

Mind you, it evaluates all parameters on the way in, so even though this checks the objTest object when assigning using it, it would still fail (when the objTest object reference is not set):

strFlavor = IIF(IsObject(objTest), objTest.flavor, "vanilla")

It's no ternary operator, but it's still indispensible for efficient VBScript coding.

Guess I'm not the only one who was baffled by the new W3C XMLHTTPRequest spec credits.

From Dare Obasanjo:

Interesting. A W3C specification that documents a proprietary Microsoft API which not only does not include a Microsoft employee as a spec author but doesn't even reference any of the IXMLHttpRequest documentation on MSDN. I'm sure there's a lesson in there somewhere. ;)

And then finally from Anne van Kesteren (one of the spec's authors):

Hereby my apologies to everyone who had to waste his time by writing a rant... The current draft reads: "Special thanks also to the Microsoft employees who first implemented the XMLHttpRequest interface, which was first widely deployed by the Windows Internet Explorer browser."

It's great that XMLHttpRequest is finally becoming an official standard.  It's better though, that the "other" browsers didn't wait for this before implementing it.  Real progress has happened as a result, in particular the recent popularity (& naming) of the AJAX technique, and the somewhat-related "Web 2.0" phenomenon.

The news also makes me smile at the anti-Microsoft folks who have thrown stones at Internet Explorer's standards support -- once again the IE team innovated (*overused word through gritted teeth*) a proprietary extension, and it was such a good thing that the competition swiped the idea, thus making it a de-facto standard.

I'd rather have a good de-facto standard now, than an official one too-late. End result: Developers and Users win (and they already are winning).

Footnote: Anyone else think it's strange that the standard's authors list seems to represent every browser except for XMLHttpRequest's inventor?