One of the things I don't like about HTML is its peculiar restrictionson anchors (elements), specifically named anchors. Named anchors are what you use tospecify the target of '#fragment' URL fragments, and the restrictionsmatter because they constrain where you can point such fragment URLs.

There are two annoying restrictions: anchors cannot be nested, andanchors must include something inside them; they cannot be empty. Thatanchors cannot nest constrains your ability to make a fragment targetwrap arbitrary content

If you're providing commercial support, I think that it is veryimportant that you actually solve your customers' problems or, if youcannot, at least realize this very fast and tell the customers.

(It is not so much because who get nothing out of their supportcontracts will stop paying for them; indeed quite possibly not .)

If you do not actually solve their problems, your customers havebecome your unpaid debuggers; in fact, they're paying you for theprivilege. This is because going

At least on the x86 architecture, shared libraries are not entirely madeup of position independent code. This means that there is a certainamount of relocation that you have to do when you load a shared libraryinto memory at run time. The basic idea behind prelinking is to try todo this relocation ahead of time; for each shared library, you pick adefault location in memory and 'prelink' it so that if it is loaded atthat location it doesn't need any run-time relocation