It's also being speculated that AMD is losing money on it's 64-bit chips. People just expect AMD chips to be cheaper than Intels, and probably wouldn't accept them otherwise.
The die size for an FX-51 or Athlon64 is stupid-big, because of larger registers/extra registers, the on-board memory controller, and the extra circuitry to accomadate 64 bits. So each individual AMD processor is larger than its Intel cousin. Check out a wafer comparison here.
As I understand it, AMD is doing this becasue it has to. Without 300mm wagers and 90nm or 65nm technology, their chips will cost too much and be produced in too little quantity for AMD to survive. It's not about whether or not AMD chips will become cheaper, its about whether or not AMD will still exist a couple of years from now.
Unfortunately, I know that many instructors have also been confused into thinking that Microsoft is moving away from OOP. The result? "Oh, we'll only skim over the object-oriented portions of C++ in this class. Most of you will program for Windows, and Windows is moving away from Object-Oriented Programming." *sigh*
I get my interpersonal skills through Slashdot, you insensitive clod!
Seriously though, why do people think home schoolers get locked into basements and forgotten? They *do* meet other children, whether through things like scouts or sports or not. We aren't a bunch of recluses, you know. We don't try to stick a floppy in someone's mouth.
It makes sense. Asia is a big market. But the thing I wonder about is whether Asia will really buy American-centric X-Box games. They're mostly a rts/rpg crowd from what I understand, and the X-Box is sold on the premise of "HALO RULES D00D!" So Microsoft will have to throw some energy into making Asia work for them.
Strange yous say this. I've been running Firebird 0.7 since it came out. It's technically still beta. But it's only crashed on me once. Perhaps you should TTFP?
When I took assembly, our textbook used TASM and MASM almost interchangeably. Yes, the syntax is different, but each operation is the same, and most of the syntax is surprisingly alike (BTW, we used a combination of MASM and VC++ in the class itself).
These two assemblers really should be considered as two different extensions of the same standard.
If it's a c/c++ compiler, the c standard states that a type 'int' stays constant. A Microsoft compiler, if following standards (a reasonable assumption) would declare a seperat, 64-bit data type.
Slashdot Mirror
But that wouldn't be geeky, now, would it?
1. Start the Registry Editor
e ntVersion \Explorer\CabinetState\
2. Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\Curr
3. Right-click an empty space in the right pane and select New > String Value
4. Name the new value Use Search Asst
5. Double-click this new value, and enter no as it's Value data
6. Close the registry editor
It's also being speculated that AMD is losing money on it's 64-bit chips. People just expect AMD chips to be cheaper than Intels, and probably wouldn't accept them otherwise.
Hell no, and I live in San Diego and even read up on the embedded scene every once in a while.
I suggest we nuke it. After all, we have plenty of them sitting around doing nothing, and what better use?
"Ooh! Ooh! Izma's in your chair!"
I have younger siblings, can you tell?
Our machines will still run without them, but the corporate customers that IBM serves won't.
That link which I was supposed to include is http://www.tomshardware.com/cpu/20040201/prescott- 05.html. A really good picture.
The die size for an FX-51 or Athlon64 is stupid-big, because of larger registers/extra registers, the on-board memory controller, and the extra circuitry to accomadate 64 bits. So each individual AMD processor is larger than its Intel cousin. Check out a wafer comparison here. As I understand it, AMD is doing this becasue it has to. Without 300mm wagers and 90nm or 65nm technology, their chips will cost too much and be produced in too little quantity for AMD to survive. It's not about whether or not AMD chips will become cheaper, its about whether or not AMD will still exist a couple of years from now.
AMD has built fabs in Germany before, it's nothing new.
I'm sorry, I should have made it more clear that I was being sarcastic.
Unfortunately, I know that many instructors have also been confused into thinking that Microsoft is moving away from OOP. The result? "Oh, we'll only skim over the object-oriented portions of C++ in this class. Most of you will program for Windows, and Windows is moving away from Object-Oriented Programming."
*sigh*
Your keyboard is different from mine. I have to simultaneously hold down the third key over from C and hit the key centered above the W and E.
I agree. C# really is just a bastardized version of Java.
I get my interpersonal skills through Slashdot, you insensitive clod!
Seriously though, why do people think home schoolers get locked into basements and forgotten? They *do* meet other children, whether through things like scouts or sports or not. We aren't a bunch of recluses, you know. We don't try to stick a floppy in someone's mouth.
It makes sense. Asia is a big market. But the thing I wonder about is whether Asia will really buy American-centric X-Box games. They're mostly a rts/rpg crowd from what I understand, and the X-Box is sold on the premise of "HALO RULES D00D!" So Microsoft will have to throw some energy into making Asia work for them.
Strange yous say this. I've been running Firebird 0.7 since it came out. It's technically still beta. But it's only crashed on me once. Perhaps you should TTFP?
When I googled, some of the stuff I got was "I Love You" related.Wierd, huh?
Confusing, as in the "little-endian" binary storage format?
When I took assembly, our textbook used TASM and MASM almost interchangeably. Yes, the syntax is different, but each operation is the same, and most of the syntax is surprisingly alike (BTW, we used a combination of MASM and VC++ in the class itself).
These two assemblers really should be considered as two different extensions of the same standard.
Am thinkink you are evil.
Hence, this will become the latest "I gotta have it!" thing for executives/bureucrats who depend on guys like us to tell them what it actually means.
Never mind me, guess I'm just cynical today. Sure, great toy.
If it's a c/c++ compiler, the c standard states that a type 'int' stays constant. A Microsoft compiler, if following standards (a reasonable assumption) would declare a seperat, 64-bit data type.
Perhaps when Valve says "next summer" they mean "next summer in the southern hemisphere". Suddenly, it starts to make sense....
This Isn't the first time Valve has done this.