Underseer said:While I agree that in general it's a good idea to update rather than not, your post is so dripping with arrogance I simply don't see the point in reading any further.
Well, then im sure its worth your time to type up a whole post to whine and complain about it...
But, obviously, providing a short informative post about the availability of a DirectX update is clearly "arrogant". Good call.
If you want people to read your entire post, it helps to not come across like an indignant 14 year old.
Well, because all the adult and "dignant" folk make sure they post to whine and complain not about the information conveyed by another person, but rather about the "style" of the information conveyance, such that it "makes them feel inferior".
You may find more people taking you seriously that way.
As opposed to being taken seriously for whining about the "arrogance of informing".
Uh huh.
PS -- does anyone know what the deal is with the version number? That's seriously weird.
Which "version number" would that be? The fact that Microsoft isnt actually updating the DirectX package version number to indicate the presence of new/revised/changed code, or the external version numbers of the D3DX9D.DLL file?
I've already explained the latter (though you might have to suffer through "informed arrogance") in another post, the former is just a Bad Decision on the part of Microsoft, thus making it difficult for consumers to determine whether they have the most recent version of DirectX.
The whole "Month X Update" naming convention for 9.0c is just..Bad.
Thankfully they finally listened to reason (after a year) and at least provided, directly to consumers for download, a cumulative package for all of the 2005 previously developer-only run-time releases.
Next.