Boots in under 20 seconds. Login prompt to responsive desktop in another 20, and some of that will be down to my PDC being a P2 [grin] No desktop icons aside from the recycle bin... no programs in the start menu apart from what Windows installed automatically (and I've already gone in and removed the games). So beautiful... now I get to corrupt it with all my applications, mwahahaha...
Um, on the subject of something worth reading. APIs. The majority of people, it seems, don't know exactly what an API is - they tend to use it as a general, catch-all term, and while it's usually perfectly simple to understand what is meant, it still annoys me.
An API is the set of language constructs - functions, structures, types, etc - that your program uses to communicate with a technology.
Right away, this gives us two important things: one, the API can be different for each language, because the available language constructs can be different. Secondly, the API is not synonymous with the technology it provides access to. "DirectX" and "the DirectX API" are not the same thing; the latter is what applications use to communicate with the former.
To bring the two points together, the majority of people on the DirectX forum use DirectX through the "DirectX C++ API", though that particular API is identical across all languages supporting COM so it's better known as the DirectX COM API.
If that's the API, what's left for the technology itself? The concept stuff. The API may give you a Surface structure and a set of functions that operate on that Surface, but it's the technology which defines the concept of what a surface actually /is/, and what those operations you can perform on it /mean./
It's not quite as clean as interface versus implementation, which is possibly why some people have trouble with it, but that's a reasonable place to start thinking about it from.
Anyway, bedtime for me...