![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#371
| |||||||
| |||||||
|
|
Robert Myers <rbmyers... (AT) gmail (DOT) com> wrote in part: On Jun 17, 10:26*am, daytripper <day_tri... (AT) NOSPAMyahoo (DOT) com> wrote: And yet you, without hesitation, characterize who I am, as if you knew me. * I do from your posts. *I'm unconvinced you know how you appear to others. *Or perhaps you seek negative feedback. At my age, I have a pretty good idea of how people react to me. With |
|
You have also "explained" to me the meaning of words uttered No. *I have explained to you the meaning I take from those words. *Your interpretation is not the only one. That's true of all words ever uttered, and it's possible that I don't |
|
by someone whom I know personally and you don't. I'm shocked you would verbally abuse someone you actually personally knew. *My estimation of you has dropped even further. I am *truly* sorry that you feel abused. My estimation of your |
|
You know *everything* with absolute certainty--except yourself. You have it reversed. *I know myself with reasonable certainty. *Everything else is doubtful. That's solipsism, and you in particular know yourself not at all, so |
|
There is no perhaps about it. *If you don't like my style of discussion, don't talk to me. *The idea that you would try to "discipline" a total stranger is revolting. You reject the basis of all society, large and small scale? Of course not. The basis of society is power and a complex set of |
|
When I get near hardware, just like when I get near other people's theories, I am sometimes able to point out things the hardware builders haven't understood because they figured they'd just "look it up in the back of Hildebrand" when they needed to. *That's my place in the world. *People who think they know what they're doing do all *kinds* of things they don't understand, sometimes with catastrophic results. Everyone _loves_ a critic. *NOT! * Your attitude even undermines your own effectiveness. I have seen many more effective critics. Where did I say that everyone loves a critic? That's ridiculous. |
|
Someone should write a book, "How to lie with data." It's pretty easy. I was written before you were born and became a best-seller: * "How to Lie with Statistics" *Darrell Huff [Norton] You really *are* clueless. I know about "How to Lie with Statistics," |
#372
| |||
| |||
|
|
Wilco Dijkstra wrote: [attribution lost] Part of the problem might also be that proprietary closed-source code such as what exists under Windows, and within Windows itself, has taken so many shortcuts that quick easy translation is not feasible. Windows itself and most of its components have been ported many times in the past to various 32-bit and 64-bit architectures, so the source code is already clean. Compiling for a different target is as simple as selecting the right switches in VC++. So why don't we see this more often? If it's as simple as selecting a different compiler switch, then it shouldn't cost too much money for an application developer to run the source through a few different switches. |
|
I also run a 64-bit Linux on all of my machines, and this version is just as well supported as the 32-bit version. Of course the big difference being that this is open-source. There is no big difference between open and proprietary in terms of porting. Either can be very easy to port or very hard, depending on how well it was written. In theory, yes. In practice, more open-source is more easily ported. |
#373
| |||
| |||
|
|
It took a lengthy, consistent string of missed schedules and dashed performance hopes just to slow it enough to give x86-64 and POWER the chance to demonstrate clear superiority: had Itanic managed to fulfill just one original promise (e.g., of significantly better efficiency due to simpler instruction scheduling) that might have been sufficient to make the world follow it where they so obviously expected to. |
#374
| |||
| |||
|
|
Bill Todd <billtodd (AT) metrocast (DOT) net> wrote in news:IMadnRLLI60Feq3XnZ2dnUVZ_hmdnZ2d (AT) metrocastcablevision (DOT) com: It took a lengthy, consistent string of missed schedules and dashed performance hopes just to slow it enough to give x86-64 and POWER the chance to demonstrate clear superiority: had Itanic managed to fulfill just one original promise (e.g., of significantly better efficiency due to simpler instruction scheduling) that might have been sufficient to make the world follow it where they so obviously expected to. I can't argue with that. I know one senior person who survived the DEC->CPQ->HP transitions. The surrender to Itanic was not just about the promised gains of Itanium, it was the 'addition by subtraction' of costs needed to stay in the workstation and server markets. Not only could DEC get rid of the burden of its own fabs, it could also get out of needeing to design, debug and manufacture the various enterprise servers, mid- range servers, low-end servers and desktops that were all deemed necessary. They were seeing such poor ROI on those efforts, they felt whatever meagre cash they could make by selling rebadged Intel boxes and services for those customers would be a better market than the ones they then held. I was told in the EV6 server era, DEC was making more money selling storage units than the servers, truly a case of the tail wagging the dog, but it was the cash that mattered. They felt if they could get a high quality server via Intel and/or HP, then selling storage and service and software would be a pretty strong business. I think the Itanic was not only its own failures to deliver, but also AMD64. The 4-way, 64-bit Opteron servers really undercut everything but the enterprise class market. Once this became clear, even Intel stoked up the x86-64 fires and back-burnered the Itanic. Fast-foward to today where we see Nehalem is shipping long before Tukwila. -- Lee |
#375
| |||
| |||
|
|
DEC never sold a single Itanium-based anything... |
#376
| |||
| |||
|
|
I just noticed (at the time) that it seemed to deliver less performance than it had been promised to do, even when measured in MIPS/GHz, and this is why I stated that it seemed to be too complex to get to work as Intel/HP hoped/promised that it would do. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |