AMD profited from Intel's boneheadedness about the Netburst architecture. Once Intel woke up, it flexed its financial muscles and developed the Core architecture.Originally Posted by zacs7
Nah, die harvesting is common practice. AMD/ATi does it, Intel does it, nVidia does it.The fact that the tri-core AMD processors are really quad-core processors that failed Q&A is rather concerning.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
AMD has a strong user-base in the budget pc market, as well as a decent hold on servers(again, because of the budget issues). Intel is getting hit left and right for various anti-trust/anti-competitiveness lawsuits which is giving AMD and nVidia a good chance to move up(AMD with the Phenom for budget performance, and the Neo X2 for netbooks and nVidia with the ION chipset replacing intel's GMA).
As CornedBee pointed out, this is common across all manufacturers. What do you think the difference between a 3.33GHz Core 2 Duo and a 3.06 GHz Core 2 Duo is? More often than not, some sort of instability that causes that 3.33 to need to be downclocked, or possibly a portion of the chache is corrupt so they downgrade a large portion of the processor and sell it for less instead of just chucking it out.The fact that the tri-core AMD processors are really quad-core processors that failed Q&A is rather concerning.
Same goes for graphics cards. If you have a card with 1600 stream processing units, and a quarter of them are bad(for whatever reason), just disable the bad ones and sell it for less as a lower model. Don't see what's so bad about that.
Only on of them failed, which is why its disabled. Theres nothing wrong with the other 3. Intel routinely sells dual core units with one failed unit as single core units. They increase yield on their quad cores by gluing two duals together (figuratively speaking). In point of fact most video cards have many failed stream processors on them.
My dad was an engineer; when I was 11, all I got for Christmas was a C64.My dad bought it for himself. For his work he said.
Right. He never again used since the day I laid my eyes on it. The day he brought it home.
I cried.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
Tears of joy I would hope, the C64 was an awesome machine in its day. In fact they sold software for it up until about 10 years ago. Its a great machine to learn on, since its simple to start programming, you cant mess anything up that turning it off then back on wont fix, and it teaches you to make the most of the resources you are given. If I was king fro a day, I'd make everyone start on a C64 or VIC-20 as their first computer and learn to program it before you could get the newer ones.My dad was an engineer; when I was 11, all I got for Christmas was a C64.
I cried.
No, mostly because previous Christmases I always got some Lego monstrosity, and had it finished before my parents got out of bed. I was up a creek wrt to assembling the C64 tho. All I could do was sit there and look at it while my stupid little sisters were laughing and playing. Also, my grandfather had died the night before...
We had a VIC20 before that. I used to program in BASIC on both of them.
I don't remember when or why I stopped -- I suspect it was a mixture of puberty and that when we got a PC clone a few years later it didn't have a BASIC oriented shell. Also cartridge games like "jumpman" on the C64 were probably a distraction.
If I was starting kids out programming on computers now, I think I'd show them ruby.
Ruby Programming Language
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
