I decided to edit this question before I read the replies... in fact before I even knew there were replies.
It is an unfair rant because it assumes tha a single case of DCX link rot implies (a) that many other cases of DCX link rot exist, and (b) that when all the rotted links are fixed they will inevitably rot again.
There's no proof that either assumption is correct.
I know (some of) the people who work on DCX, I know they care about this stuff.
So... you've been warned... and here's the original rant:
This link worked on April 24, 2009, and now it no longer works...
That means I have to fix this blog post: http://sqlanywhere.blogspot.com/2009/04/demonstrating-high-availability.html
I have two choices: Update the link to DCX, or remove it altogether.
I am leaning towards Door Number Two: no more links to DCX... that's generally how I deal with websites that are prone to link rot.
Does anyone have a better idea?
The issue is fixed. Sorry about that, Breck!
We definitely want links to be backwards compatible, so if you do see any other issues with linking (or anything dcx-related for that matter), you can always let us know by sending an email to firstname.lastname@example.org.
answered 04 Oct '10, 18:10