Here's your first caveat... "to developers" which is a tiny community in the
software world. "To developers" isn't even accurate. It's only
"developers" that have cared to get involved in early development. That's
an even smaller group. Name the software standard that wouldn't call this
vapor? Since you've acknowledged that this is a standard, please list it!
You can try twisting what I've said around all you want, it won't change
the fact of what "built" means. I did not say there was a standard for
vapor in terms of software so I won't get sucked into that thank you. I've
worked in software for a long while and I consider it "built" when I have
first versions which function as designed. Call that an Alpha version if
you like - it is "built" IMO and the opinion of most people I've worked
with.
There is still work to do of course but in this context, Windows XP-64 for
x86 is still way beyond Alpha... more like RC-final if you're cynical about
M$'s relationship with "i". Linux also is way beyond "built". Oracle has
already announced, months ago, that it took 2-3 days to recompile and have
a working version for Linux - no mean feat when you consider the code size.
Only people internal to Oracle know how close it is to ready for release to
users... who are not, despite your presumption, part of the "software
world".
Digital cameras doesn't make them wiser... LOL. None the wiser for
anything. If you can work a VCR, are you an expert on electronic
engineering? That's quite a leap of faith.
Entirely *your* leap though... with a ludicrous analogy. Sure there are
many who have the ubiquitous flashing 12:00 symptom in the world of VCRs.
People who have digital cameras *do* get to appreciate the effects of large
files and the impact of processing of them for various photo-effects they
want to achieve... and no, I'm not talking about someone with a 2Megapixel
snapshot job.
It is wholly untrue also. Most
consumers don't know what 64-bit gets them. It's just another catchy
buzzword to them. If the consumers were intelligent, they would probably
shun the 64-bit for a marked down 32-bit since there is little to be gained
from having 64-bit at this moment for most consumers.
You surely *do* acknowledge that we're both speculating here - there's no
right or wrong. We'll see what the truth is eventually. Once again, you
seem to have illustrated how out of touch you are with reality: there is no
need for "marked down" to get a 64-bit Athlon64 CPU - the CPUs *and* mbrds
are in the same $$ ballpark as the Athlon XP versions and the Intel P4s.
The system incremental cost, market segmentation notwithstanding
, is
negligible and the benefits of the new AMD 64-bit ISA are far more than a
simple addressability extension... but I'm sure you knew that.;-)
Yes, I saw that long ago. It was a reach by most estimations but we all
kept it in the back of our minds anyway.
Obviously it was *no* reach! If you were part of "most estimations" you
were wrong back then. Personally I was quite convinced.
It was known more than 2 years ago
that Intel was working on Yamhill but would only release a product if they
had to (market pressure driven by media frenzy for a new buzzword). I'm
still shocked about it being a 3rd quarter 2004 product though. It seems a
bit hasty but perhaps their partners were pushing it hard (such as Dell)
and the sales numbers looked right for it.
It was also known that Intel denied the existence of Yamhill. Undoubtedly,
Michael Dell is now cleaning out his drawers... err shorts... hard to say
on that last.
Rgds, George Macdonald
"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??