Slashdot Mirror


CPU Wars

msolnik writes: "Whether you say "0.13-micron" as most of us do, or "130-nanometer" as PR flacks prefer, the phrase is weighing heavily on both Intel's and AMD's minds. Indeed, each company's timeline in reaching that mark may determine who calls the CPU shots in 2002. Read more here at Hardware Central." Other submitters noted that AMD and Motorola have both updated their development roadmaps.

177 comments

  1. Half a mil? by CmdrPaco · · Score: 0, Redundant

    How about instead of 130 nanometers, they say half a mil? Guess nobody knows what a mil is?

    --
    I bet this is not "First Post."
    1. Re:Half a mil? by Anonymous Coward · · Score: 4, Funny

      A mil is approximately 592 meters.

      You get that dividing a "mile" (1609 m) by "e" (2.7183).

    2. Re:Half a mil? by Tet · · Score: 1
      A mil is approximately 592 meters. You get that dividing a "mile" (1609 m) by "e" (2.7183).

      This is one of those times I really wish I wasn't out of moderator points...

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    3. Re:Half a mil? by Anonymous Coward · · Score: 0

      LOL!
      Mod this up, please.

    4. Re:Half a mil? by Anonymous Coward · · Score: 0

      Wouldn't it be 1606.282 meters? That's a "mile" (1609) - "e" (2.718)

    5. Re:Half a mil? by Mattsson · · Score: 1

      Well... Actually, a "mil" is 10 kilometers. :o)

      --
      /.Mattsson - My native language is not English, so please don't whine over linguistic errors. (That's lame anyway...)
    6. Re:Half a mil? by strathconaman · · Score: 1

      Actually, a mil is the angle made by an isosceles triangle with 1000m long sides and a 1m base. Oddly enough, there are 6400 of these in a circle. It is used in navigation, and for determining the distance to objects of known size.

  2. Intel 4004 anno 1971 by Hougaard · · Score: 5, Informative
    The 4004 consists of 2,300 transistors based on 10 micron technology fitting on a 12mm2 area.The microprocessor has 46 instructions. The 4040 is an enhanced version of the 4004, adding 14 instructions, larger stack (8 levels) and 8K program space. It can address 640 bytes. Documentation is written by Adam Osborne. The chip is introduced to the public in Las Vegas by Wayne Pickette. The sales price will be US$ 200 per piece.


    This was the news of 1971

    1. Re:Intel 4004 anno 1971 by Hougaard · · Score: 1

      10 micron vs. 0.13 micron, we have come a long way since 1971. 76 times smaller..

    2. Re:Intel 4004 anno 1971 by Hougaard · · Score: 2, Informative

      76.923076923, but the interesting thing is, that its both horizontal and vertical so its actually 5917.1597633 times better on the same square-inch.

    3. Re:Intel 4004 anno 1971 by stud9920 · · Score: 1
      76.923076923, but the interesting thing is, that its both horizontal and vertical so its actually 5917.1597633 times better on the same square-inch.
      Even more amazing is the fact that thirty years represent 20 Moore law generations. If we take this into account, we should have had a 2^20 = 1,000,000 factor, yet we only reach 6000. Even if we take into account the fact that we now take some 120 mm2 instead of 12 mm2 (ten times more), we still are log2 1e6 - log2 60,000 = 4 Moore law generations backwards ! That's six fucking years ! And you can add five more years if we stay at said 12 mm2.

      At least, things are less serious as for the CPU clock : from four kHz to two GHz, it's only one generation backwards.
    4. Re:Intel 4004 anno 1971 by superflex · · Score: 1
      arrr... yet another misinterpretation of Moore's Law...

      Moore's Law - (moo-urhz lah) n. 1.Famous statement by Intel founder Gordon Moore. Moore predicted that the number of transistors per integrated circuit would double every 18 months. See here.

      Moore's law says nothing about the number of transistors per unit area doubling every 18 months. Only transistors per IC; and a Pentium IV is a hell of a lot bigger than a 4004.

      --
      sigs are for suckers
    5. Re:Intel 4004 anno 1971 by stud9920 · · Score: 1

      Excuse me to have cited by heart, but I DID make the jump to the #transistor/die, when I talked about the 12 mm2 to 120 mm2 jump.

      If you really want to count by transistor, we come from 2300 transistors on the 4004. We should thus expect 2.3 milliards transistors on the last generation, but instead we stick with a lousy 50 millions last time I checked. That's 20 times too few, or about 7 moore law generations. 10 fucking years, even worse than I told you. Thanks helping me making my point.

    6. Re:Intel 4004 anno 1971 by stud9920 · · Score: 1

      Oops sorry, I meant 40 times too few (8 moore law generations, 12 years)

    7. Re:Intel 4004 anno 1971 by Anonymous Coward · · Score: 0

      If I recall correctly, Moore's law initially only applied to memory, not microprocessors. It has evolved to apply to microprocessors, but it wasn't neccesarily valid for uProcessors for the first several generations.

      Also, in the same way, I believe the initial time period was 24 months, but it ended up speeding up after a while. So, there are actually fewer generations between then and now.

    8. Re:Intel 4004 anno 1971 by renehollan · · Score: 2
      stud9920-speak:

      Your error: "#@$@#$ @#$@#!4 fuc@#@# years!!!"

      My error: "oops... sorry"

      /me can't help but laugh. (Oh hell, my karma's so high, I could stand a few -2, pedantic).

      --
      You could've hired me.
    9. Re:Intel 4004 anno 1971 by Anonymous Coward · · Score: 0

      well, recent Itanium (if you can get one) is
      320 million...something like 420mm2 and 130watts
      TDP..

    10. Re:Intel 4004 anno 1971 by Da+Schmiz · · Score: 1
      The actual quote, from Moore's paper, is:
      The complexity for minimum component costs has increased at a rate of roughly a factor of two per year (see graph on next page). Certainly over the short term this rate can be expected to continue, if not to increase. Over the longer term, the rate of increase is a bit more uncertain, although there is no reason to believe it will not remain nearly constant for at least 10 years. That means by 1975, the number of components per integrated circuit for minimum cost will be 65,000.

      I believe that such a large circuit can be built on a single wafer.

      So, you're wrong: the doubling period Moore initially predicted was 12 months; this held true for the 10 years that Moore originally estimated, and then dropped to 18 months not long afterward. The definition from the Jargon File:

      Moore's Law /morzlaw/ prov. The observation that the logic density of silicon integrated circuits has closely followed the curve (bits per square inch) = 2^(t - 1962) where t is time in years; that is, the amount of information storable on a given amount of silicon has roughly doubled every year since the technology was invented. This relation, first uttered in 1964 by semiconductor engineer Gordon Moore (who co-founded Intel four years later) held until the late 1970s, at which point the doubling period slowed to 18 months.
      --

      "Anything is better than IE, and you can quote me on that." -- Wil Wheaton.

    11. Re:Intel 4004 anno 1971 by Anonymous Coward · · Score: 0

      What the fuck is a milliard? Isn't that french for billion?

  3. One thing's for sure. by AFCArchvile · · Score: 1

    Now matter who hits 0.13 first, WE win.

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  4. Mac Hype by BiggyP · · Score: 2, Insightful

    bloody hell, they really are hyping the G5, and they haven't got any confirmation of what technologies it will use, they simply assume that motorola's latest chip will be the basis, how much would you have to pay for a mac for them to make returns on their production process?

    1. Re:Mac Hype by Thaidog · · Score: 0

      Supposed to 64bit with 32bit back compat. But like you said.. wat to many rumors... like this one: a 400mhz bus... the newest spec I've seen.

      --

      ||| I still can't believe Parkay's not butter.

    2. Re:Mac Hype by Spruitje · · Score: 3, Informative


      bloody hell, they really are hyping the G5, and they haven't got any confirmation of what technologies it will use, they simply assume that motorola's latest chip will be the basis, how much would you have to pay for a mac for them to make returns on their production process?


      Well, actually.. A G5 powermac will cost almost the same as the current G4 machines.
      The PPC8500 is a 64 bits processor which is 100% backwards compatible.
      I've seen some preliminary SpecFP and SpecINT figures and if those are correct a PPC8500 running at 1,6 Ghz is equal to a P4 running at 3 Ghz.
      It is twice as fast as a Itanium running at 80 Mhz. and uses only 15 watts peak.
      Compare that with around 60 watts for a P4 running at 2 Ghz..
      The difference with this chip is, that most of design work was done by Apple itself.
      This chip uses 0.13 micron technology and SOI.
      So ,actually the dye size is almost equal to that of the G4 which means that it will cost almost the same.
      Don't forget that the PowerPC chip is based on the Power architecture of IBM.

    3. Re:Mac Hype by Anonymous Coward · · Score: 0

      "1,6 Ghz is equal to a P4 running at 3 Ghz."
      you keep telling yourself that and one day it may even be true, but you can get out and push your 1.6ghz powerpc chip and its not gonna be as fast as a pentium 4 at 3ghz. sure in some specially optimized applications that 1.6 may perform "as good" but quit outright denying the truth that in most things the pentium 4 will be faster. Write code and do your own tests, you'll see I'm right.

  5. Re:Intel 5975 anno dominus by Anonymous Coward · · Score: 0

    Currently spiky, but turning to '69 dood' later today. Hast du meinen wald?

  6. Fast CPUs might be bad. by Krapangor · · Score: 0, Troll

    People always get exited at faster and faster CPUs.
    But what is the use ?
    Ok, it's a good marketing argument to make people buy new computers every 2 years.
    But is there any significant advancement in computer programs ?
    You would now say Quake and CS but these are only a few games. And most their functions could be spend up by dedicated co processors (this arguments is around for years but always stompe up by Intel and AMD to make people buy their expensive new processors).
    And graphical user interfaces ?
    These were running on old macs which had only 5 percent of the processing speed of modern cpus.
    Are programs becoming more useful ?
    Most software is today just silly bloatware, you need several 100 MB of storage for a program which fullfill just the functions a 2 1.44 MB floppys program did in 1990.
    There is also an unholy connection to OO.
    Programmers take often OO as an excuse for bloated (which is not the same a reusable) and uneffective code. When their program is too slow the don't fix this, they just claim that the computer is too slow.
    And perhaps AI ?
    This is nonsense, too. Most AI problems are in the core at least NP complete, sometimes even PSPACE.
    So just speeding up the CPU doesn't help anyway, we need totally different computer models for such problems, e.g. read the recent slashdot article about ants (hello hex).

    So the CPU capacity increase is just a scam from the computer manufacturers. We should boycott this and it can be done: we just make our open source software compatible to old system and let AMD and Intel to starve in the desert.

    --
    Owner of a Mensa membership card.
    1. Re:Fast CPUs might be bad. by Anonymous Coward · · Score: 1, Interesting

      But don't you get a thrill out of the fact that you nearly have more processing power on your desktop than the entire world did twenty years ago?

      It makes scientific research incredibly simpler/cheaper, and that is worthwhile on its own. If you've much patience, a 486 running windows 98se and Office '97 is still fully functional, I use one as my backup desktop system.

    2. Re:Fast CPUs might be bad. by macragge · · Score: 0, Insightful

      With the recent entrance of the seccond generation MMORPG on the gaming front, processors that were considered decent no more then six months agao are now not even worthy of the title 'decrepit'. Games like Anarchy Online, Starwars Galaxies, and Dark Age of Camelot, only to name a few, are pushing the benchmark higher and higher for gamer.

      If MMORPGs dont suit your taste, take a look at a few new less eppic games such as Giant: Citizen Kabuto from early last year, people couldnt run that with all the widgets and gizmos cranked up to the maximum level, I could barely even play it on my PIII 500, and that was almost a year agao. Now-a-days we have we have to look out for games like Civ3, and Aliens Vs. Predator 2, recent titles that managed to make a bitch out of a 1GHZ box. Sure these games arn't exactly the crem de la creme of efficient software, but they are what we have. Rather then praying for a revolution where we hold developers by the neck and tell them to slow down their development I say that we should support them. All though new games are beutiful, they don't compare to the Enterprise's Holodeck.
      Now unless you can show me a cost effective meathod that will speed up games and make them run on my old P2, I suguest that you quit your bitching. I for one want a system that will allow me to crank up the realism and not come to a screaching halt.

      Now if you hate your bloated software, don't use it. You can get by without any of it, throw linux on your 486, surf the net with w3m, write your efficient code in vi, and use pine to send me a letter telling me how wonderful the world was before the evil corparation forced you to buy you a faster computer.

      Untill you are prepared to throw away all of your nifty little gadgets that showed up with faster processors, don't complain. Play your old games, listen to your .midis and don't try to stop inovation.

    3. Re:Fast CPUs might be bad. by GroovBird · · Score: 5, Insightful

      Well IMHO you're not really correct. All this is relative to what you're used to work with.

      You're only naming two games, both using the same engine, that are now approx. 5 years old. These days all games are trying to be as immersive as possible, using 3D graphics and sound, enhanced with special FX, and playing against an army of bots trying to mimic our behaviour. They are already using dedicated coprocessors (called GPU's these days).

      GUI's have evolved from crappy crammed black and white boxes with hourglasses to 24-bit 1280x1024 alpha-blending anti-aliasing semi-intelligent "interfaces". This all takes memory, memory bandwidth and CPU cycles.

      I find myself amazed, even as a software developer, that these days I can take pictures with my digital camera and send them to my mom using e-mail. I predicted this could be done a long time ago. But now I'm doing it I have to stop at moments and find myself simply stunned by the world we live in. We're ordering pizza's from our PCs using broadband network connections. My audio software (Propellerhead's Reason) can emulate a jampackked rack of synths and samplers, and the sound is generated in realtime. I don't have a digital camcorder, but if I owned one I'd spent my nights making my own movies. Picture this 10 years ago.

      If you think OO is what makes softwar bloatware then you don't understand OO, in my opinion. OO is one of the ways to achieve true code reuse, which is what we're all striving to do because we are all lazy asses. Code reuse means you get a lot more done in less time, and if done right it should take less space all at the same time.

      What really makes software 'bloatware' is the addition of functionality beyond what is needed by the majority of the users. But then again the markets have widened and software has become one of the biggest business in the world today. More users want to find software useful and software vendors respond with more and more features which will always sound like bloatware in the eyes of a few geeks who like to hack together their own kernel and run it on your average pocket 'PC'.

      Sure games were fun 20 years ago just as they are fun today. I like to play tetris myself a lot of times but if you really think about it, same now as back then, only 5% of all games are classics and 95% are crap. We're all just spoiled now and the only reason we'll play pong is because it makes us feel nostalgic.

      In 10 years you'll say that you don't need the latest AMD XP 22000+ (16Ghz nominal) with 512GB of battery-backed-RAM and a semi-optical harddisc of 600TB ... but then again you'll always be saying this.

      I say, keep 'm coming.

      Dave

      Personally I'd never go back to the days where i had to wait

    4. Re:Fast CPUs might be bad. by Stormie · · Score: 0, Troll

      Yay, karma whore.

      The instant I saw this story on the front page, I knew one of the first comments would be "what's the use of faster CPUs blah blah blah software is bloated blah blah blah I don't need it blah blah blah". And I knew it would be modded up as interesting, insightful, etc.

      It's not interesting and it's not insightful. It's an utterly banal and uninteresting observation, that some whore trots out every time Slashdot runs a story that hints that CPUs in the future will actually be faster than CPUs today. Moderators, don't encourage it, please!

      Krapangor, go home. If you don't want a faster CPU, we don't care. Some people will be buying or upgrading next year, and the fact that AMD and Intel both hope to be on 0.13micron process early in the year is stuff that matters to them.

    5. Re:Fast CPUs might be bad. by Weh · · Score: 3, Interesting

      for every more powerful cpu to come out there's people saying we don't need it. I wonder how long it has been going on? Windows 3.11 was nice on a 486 66Mhz but I'm sure happy that chip development didn't stop there.

      I think it would be interesting to see the effect of CPU power on software pricing. With faster CPUs software might be less optimised thus costing less programmer time. It's just a thought...

    6. Re:Fast CPUs might be bad. by ceeam · · Score: 1

      While there are programs that run slow there will be a demand for faster CPUs (and systems in general). That's it.

    7. Re:Fast CPUs might be bad. by squaretorus · · Score: 1

      On a tangent, but hopefully not off the topic!, has anyone else been telling their 'we want to get on the internet' family and friends to buy OLD PCs?

      I've pointed people at PII machines in the 400-700MHz range. These can be picked up for about 250-300UKP and do everything most people need. If they need a faster machine in a couple of years they can buy a 1.6GHz machine for about the same money most likely.

      The alternative that PC world is putting forward costs significantly more, for minimal noticable additional performance. 750-900UKP is the price point the retailers seem to have picked for a Xmas PC for the family. For this you get:

      -- AMD 1600XP Processor
      -- 256Mb DDR Ram
      -- 80Gb Hard Drive
      -- DVD & CD Rewriter
      -- 64Mb F3 200 Titanium Graphics
      -- 56K Modem
      -- Windows XP Home Edition
      -- Lotus Smartsuite
      -- 17" Monitor (15.7" viewable screen)

      Barring the CD cutter all you are getting for your additional 500UKP is a greater excess of speed, HD, etc...

      For the average family PC yu really don't need the speed.

    8. Re:Fast CPUs might be bad. by Junks+Jerzey · · Score: 2

      With the recent entrance of the seccond generation MMORPG on the gaming front, processors that were considered decent no more then six months agao are now not even worthy of the title 'decrepit'. Games like Anarchy Online, Starwars Galaxies, and Dark Age of Camelot, only to name a few, are pushing the benchmark higher and higher for gamer.

      MMORPGs are more dependent on *bandwidth* than anything else. You're just talking about the 3D side of things.

      look at a few new less eppic games such as Giant: Citizen Kabuto from early last year, people couldnt run that with all the widgets and gizmos cranked up to the maximum level, I could barely even play it on my PIII 500, and that was almost a year agao.

      That's because 90% of the time in games like that is spend inside of a 3D driver. Switch the game to pre-assembled display lists (i.e. "use the transformation capabilities of the card") and you'll get a 10x speedup on the same machine. The trouble is that game developers can't assume such a card, as there are lots of entry level machines that are shipping with bare-bones 3D capabilities.

    9. Re:Fast CPUs might be bad. by archen · · Score: 1

      noting that faster processors make up for sloppy programming, there are also other needs as well. "Back in the day" you had components that to some extent ran themselves. Nowdays many of these components (modem, on-board sound, etc) freeload off the processor in order to reduce costs. Many benifits you don't even think about until you actually see them. Encoding an album of mp3`s on my 133Mhz computer used to take well over two hours. On my 1.4Ghz Athlon I can encode an album on OggVorbis in something like 8 minutes.

    10. Re:Fast CPUs might be bad. by arkanes · · Score: 1

      Staying a year or 18 months behind state of the art is about the best balance for the common user. Heck, MOST games will play fine on a system that old. I buy a lot (lot!) of my games off the 9.99 rack at EB, and I find that I generally get at least as much play value out of them as I do any of the $50 games. And they'll run great on a PC thats a couple years old.

    11. Re:Fast CPUs might be bad. by Simon+Peters · · Score: 1

      Too right. I sorted out my parents' PC a couple of years ago. A Cyrix 300 with 64 meg ram, 4 gig hard drive. The only thing that has needed replacing was the CD-Rom drive. total cost including replacements: gbp350. They are still more than happy with it.

    12. Re:Fast CPUs might be bad. by LoonXTall · · Score: 1

      No way! Faster CPUs give you a higher BogoMIPS rating! And besides... the working set of some programs is small enough to fit in cache (both L1 and TLB), and gain a proportional performance advantage from increased CPU speed (after being optimized for the core.)

      --

      ~~~LXT~~~
      Life is like a computer program: anything that can't happen, will.

    13. Re:Fast CPUs might be bad. by Tackhead · · Score: 2
      > has anyone else been telling their 'we want to get on the internet' family and friends to buy OLD PCs?

      Yes, yes, yes, yes, yes!

      For those of you who have a nearby surplus store, go there.

      Sample upgrades: I saw a $30 P166MMX system that happened to have an Asus TX97 motherboard. A free upgrade to the beta 0112 BIOS from the 'net. A $30 K6-2+-450 laptop chip, or a K6-3-333 are drop-in replacements for the P166MMX, and offer performance comparable to a PII in the same speed range. Such a system is a great place to toss that stick of 64M PC100 SDRAM you're not using anymore, as well as that 8.4G hard drive you just replaced.

      I did that upgrade for my own box and it's capable of doing all-software DVD on a cheap-azz 4M ATI TV-out card from 1996 with no DVD hardware support.

      Want monitors? Surplus stores rule. I was in one yesterday and picked up a 19" Sony true-flat CRT for $120. (Pricewatch: $400-500). They had 17" Sony flat-CRTs for $70 (Pricewatch: ~$300). There were also several 21" monitors (Viewsonic P815, Pricewatch $700 new, $325 refurb) for ~$200.

    14. Re:Fast CPUs might be bad. by Sj0 · · Score: 1

      I'd just like to point out that gamers don't need the latest and greatest hardware either. How many games don't run just fine on an Athlon 700 with a Geforce 2?

      The whole tech thing above a gigahert is just posturing and such, especially if it's for games. The only thing I could think of which would need as much processing power as we have would be either a server or some scientific problem, but even then, the space shuttle was landed on the moon with technology so feeble compared to todays, I'm not entirely sure of that.

      I'm not complaining about this whole chip war driving down prices on the CPUs I actually want to buy though :)

      --
      It's been a long time.
    15. Re:Fast CPUs might be bad. by Sj0 · · Score: 1

      I find myself amazed, even as a software developer, that these days I can take pictures with my digital camera and send them to my mom using e-mail. I predicted this could be done a long time ago. But now I'm doing it I have to stop at moments and find myself simply stunned by the world we live in. We're ordering pizza's from our PCs using broadband network connections. My audio software (Propellerhead's Reason) can emulate a jampackked rack of synths and samplers, and the sound is generated in realtime. I don't have a digital camcorder, but if I owned one I'd spent my nights making my own movies. Picture this 10 years ago.

      I *was* doing it 5 years ago, and it took way less hardware than you might expect. I was watching TV on my less than state-of-the-art 386sx with 4 megabytes of RAM, using a 15 year(at the time) old video capture card and a VCR. I took pictures using a camcorder which gave sharper images than digital cameras have been able to dream of until recently.

      I wrote MIDIs using some anonymous shareware program and made them sound great using WinGroove, in realtime.

      The best part of all this is that my computer was 6 years old at the time. I could have easily done any of these things when I first bought the computer, running Windows 3.1 in 1990. The video capture card existed, the internet existed, the sound card existed, and it would all run on a 386. Perhaps expensive for the time, but considering how many tens of thousands of dollars many have spent on upgrading to get these abilities over the years, it would have been money well spent.


      In 10 years you'll say that you don't need the latest AMD XP 22000+ (16Ghz nominal) with 512GB of battery-backed-RAM and a semi-optical harddisc of 600TB ... but then again you'll always be saying this.

      The only time I haven't said this was when my PC wasn't capable of doing what I told it to do. The 8088 was too slow for my needs. The 286 was close. The 386 was a rocket. It's all just extra layers of junk from there.

      Believe it or not, for most peoples needs, a suprisingly old computer will do the job.

      --
      It's been a long time.
    16. Re:Fast CPUs might be bad. by whopis · · Score: 1

      Not to question your wisdom... but as I recall, the space shuttle never landed on the moon...

    17. Re:Fast CPUs might be bad. by boopus · · Score: 1

      Have you ever tried to render slashdot on a 386? I won't say it can't be done, but it won't be a fun wait. An old pentium 120 running opera is nearly unbearable. So for your sake, I hope you're happy with lynx.

    18. Re:Fast CPUs might be bad. by Sj0 · · Score: 1

      I did. I did all that fun stuff using a 386. Web surfing was fine.

      Besides, waiting for the huge slashdot pages to *load* will take pretty long on my dialup connection. :)

      --
      It's been a long time.
    19. Re:Fast CPUs might be bad. by Sj0 · · Score: 1

      um......oops.

      I was too busy ranting to notice. My point remains that we landed on the moon (without the shuttle :)) decades ago.

      If the shuttle were to try to land on the moon, I'm pretty sure the result would be grizzly, to say the least. :)

      --
      It's been a long time.
    20. Re:Fast CPUs might be bad. by BryceH · · Score: 1

      Programmers take often OO as an excuse for bloated (which is not the same a reusable) and uneffective code. When their program is too slow the don't fix this, they just claim that the computer is too slow.

      I dont disagree that software is bloated, but i do think that you have the wrong impression of OO. OO is simply a method of designing projects for reuse, easy understanding by other designers, and as a bonus it helps in dividing up tasks for the programmers. It really 'should not' lead to overly bloated software. When OO yeilds substantialy slower software the design and/or implementation is at fault, not the method (you cited programmers. that 'sort of' underscores my point. OO is a software engineering method, best implemented by.. software engineers, not programmers. in the extreem, programmers dont even need to understand OO or know what it is. They just need to program efficient modules). IMHO The real culprit is the "feature" overload in most of that newfangled "inovative" software.

      --
      "Shut up brain or ill stab you with a Q-tip" Homer Simpson
    21. Re:Fast CPUs might be bad. by Pyrrus · · Score: 1

      no, it'd go ok... the take off and return to earth might
      pose a bit of a problem though

    22. Re:Fast CPUs might be bad. by mgblst · · Score: 1

      People always get exited at faster and faster CPUs.

      This is the way of the world, not just for cpus. People get excited about new cars, that are no different than old cars, about big tvs, new stereos, all differing from the previous only slighty. You had better be careful what you say, or your likely to be labeled a communist!

    23. Re:Fast CPUs might be bad. by lcracker · · Score: 1

      Real musicians aren't content with cheesy software wavesynths, not to mention that WinGroove probably worked at 8bit 22khz, and not the 16 or 24bit 44.1khz+ requred for professional recordings.

      Sure it was possible on a 386 (ram and hdd space limiting), but it sure as hell wasn't realtime.

  7. Nanometers ahoy! by Visoblast · · Score: 3, Interesting

    Before we get to 0.09 microns, lets start using nanometers to get rid of those preceding decimal places. Plus, unlike micron, a nanometer is an accepted SI unit (see http://physics.nist.gov/cuu/Units/prefixes.html). Strange the PR people should use it first -- could this be a sign of the Apocalypse?

    --
    "Luncheon meats make the sawdust in your stomach explode."
    • -- Crow T. Robot
    1. Re:Nanometers ahoy! by Anonymous Coward · · Score: 0

      i think micron is a common abbreviation for micrometer, which is an accepted SI unit, no ?

    2. Re:Nanometers ahoy! by sjwt · · Score: 0

      Why mircons anyway?
      0.13 mircons = 130 nm..

      perhapes it was cause at the time,
      ppl where still touchy of metric :)

      an no one wanted to be useing billioinches :)

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
    3. Re:Nanometers ahoy! by FrankDrebin · · Score: 1
      Strange the PR people should use it first -- could this be a sign of the Apocalypse?


      Better a PR hack than a NASA engineer!

      --
      Anybody want a peanut?
    4. Re:Nanometers ahoy! by agdv · · Score: 1

      The word "micron" is merely an abreviation of "micrometer," which *is* an accepted SI unit. But I agree; the reason why there are submultiples in the first place is to avoid the 0.00... at the beginning. But until someone comes up with a marketable abreviation ("nanon"?) for nanometer, we're stuck with it.

  8. Industry question by Boiling_point_ · · Score: 1

    I know nothing about the chip manufacturing industry so I'll put my newbie propeller-cap on for a moment.

    Nothing in that article tells me whether what they are doing (constructing really fast chips) is really that hard - in a scientific sense. Is it simply an engineering challenge? What spin-off technologies are likely to result? What's going to come 'next' from all this, apart from more chips?

    --
    "If you create user accounts, by default, they will have an account type of Administrator with no password." KB Q293834
    1. Re:Industry question by superflex · · Score: 1
      The challenge of producing chips with smaller and smaller feature sizes is the difficulty in using photolithographic techniques effectively.

      Photolithography is how IC's are made. The process is kind of similar to silk-screening. Masks of the various layers of the chips are made. Chemicals are deposited on the surface of the chip. Light is shone through one of the masks, and focused with lenses onto the chip. The chemicals react to exposure to light, so the portions of the layer of chemicals on the chip that were exposed to light through the mask are now different from the dark masked sections. Depending on the process, now, either the light- or dark-exposed chemicals can be etched away with acid, leaving the oppositely-exposed regions intact. This is done repeatedly to lay out components and interconnections on chips.

      The hard part in reducing feature sizes is that the wavelength of the light being used becomes a limiting factor in size reduction. Decreasing the wavelength to x-ray scales can do funny things to previously effective techniques of masking and focusing, due to refraction and other effects. These are the areas currently under research by chip makers, using techniques like xray and electron-beam lithography to allow further decreases in feature size.

      --
      sigs are for suckers
    2. Re:Industry question by Shuh · · Score: 1

      The design is an engineering challenge, a management challenge, and a scientific challenge. The engineering and design for a processor actually *lead* the technology needed to make the chip by a few years. So when a chip like the G4 or P4 is first started, engineers and managers and such have to *guess* what people are going to be wowed by in 3 or 4 years and what fab technology might be available to deliver it to them at that time. The science comes in when things "don't quite work out like we hoped..." ;c)

  9. Next year by The+Gardener · · Score: 4, Funny

    Next year looks like the best time ever to buy a new performance PC.

    Well, duh. Just exactly like every year since they were invented.. And just like every computer magazine pundit has said since day one

    The Gardener

    --
    --
    1. Re:Next year by blair1q · · Score: 2

      And have they ever been wrong?

      --Blair

  10. Smaller die == less heat? by tnak · · Score: 2, Interesting

    Ok, I admit it. I'm confused. I thought a smaller die size increased heat. Less surface area to radiate from.

    Gotta love the last line:

    Next year looks like the best time ever to buy a new performance PC.


    Next year is always the best time to buy a new PC.

    1. Re:Smaller die == less heat? by Anonymous Coward · · Score: 1, Informative

      Smaller die = smaller circuits
      Smaller circuits use less power and generate less heat.

    2. Re:Smaller die == less heat? by Anonymous Coward · · Score: 0

      Due to less power consuption.

    3. Re:Smaller die == less heat? by Anonymous Coward · · Score: 0

      >Less surface area to radiate from.

      That would increase heat per unit area (J m^-2) rather than total heat dissipated (J).

    4. Re:Smaller die == less heat? by G00F · · Score: 1

      What they say (about less power) and the fact there is less friction in the cpu for the power. Less friction = less heat as well. (thats why they need to get to a smaller die size for more mhz)

      --
      The spirit of resistance to government is so valuable on certain occasions that I wish it to be always kept alive
    5. Re:Smaller die == less heat? by Anonymous Coward · · Score: 0

      die is not the same as transistor.

    6. Re:Smaller die == less heat? by bn557 · · Score: 1

      but if you have a (relatively) constant heat per area, and you lower the area, you lower the total heat you can disapate over time.

      Pat

      --
      Humans are slow, innaccurate, and brilliant; computers are fast, acurrate, and dumb; together they are unbeatable
    7. Re:Smaller die == less heat? by NerveGas · · Score: 2

      Ok, I admit it. I'm confused. I thought a smaller die size increased heat. Less surface area to radiate fromm

      You're confusing temperature with heat. : )

      Both points of view are actually right. In the ideal world, having smaller transistors lets them operate at a lower voltage, so you use less power, and generate less heat. And if the die is smaller because of a decrease in transistors, you still use less power.

      In the real world, though, you don't see Intel shrinking their dies and then leaving them at 650 MHz. When they shrink the manufacturing process, they also increase the frequency, offsetting any decrease in power usage. And, over the long run, they also increase the NUMBER of transistors, making it use even more power. So while the textbooks say that the new chips will use less power, they're likely to use MORE power, especially when they've had time to ramp them up to the higher clock speeds.

      steve

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
  11. get your terms correct by Michael+Wardle · · Score: 1

    0.13-micron...

    The term micron has been deprecated for over 20 years. The correct term for millionth of a meter is micrometer, symbol .

    1. Re:get your terms correct by Michael+Wardle · · Score: 1

      Sorry, the symbol's m.

    2. Re:get your terms correct by chrisvr · · Score: 1

      Except that no one that I know ever uses micron. The only time that I ever had a problem with the micron/micrometer bit is when I wrote a scientific paper that had to be reviewed by NIST (National Institute of Standards and Technology).

      Now, Angstrom is definitely on its way out... unless it isn't.

    3. Re:get your terms correct by chrisvr · · Score: 1

      Whoops-- I meant that no one ever uses MICROMETER.

      I knew I should have previewed...

    4. Re:get your terms correct by Tet · · Score: 3, Insightful
      I meant that no one ever uses MICROMETER

      No, but we do use the micrometre. The same way we use microfarads, microseconds and microvolts. I guess in the US you still use microns, but then you still use feet, inches, pounds and ounces, too. You have a perfectly good system of SI units, so why not use them? At least micron is just another name for a valid SI unit. Unlike Angstroms, which are just an abomination against nature (they should have just used nm or pm as appropriate).

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    5. Re:get your terms correct by Xilman · · Score: 1
      Unlike Angstroms, which are just an abomination against nature (they should have just used nm or pm as appropriate).


      Except when the Angstom unit was invented, all this micro, nano, pico stuff was still well in the future. The Angstrom unit is actually well designed: it's 1e-10 metres and it's about the size of an atom, which fits well with its original usage in atomic and molecular spectroscopy.


      Paul

      --
      Lasciate ogne speranza, voi ch'intrate
  12. it's a bird, it's a plane... by Chundra · · Score: 0, Flamebait

    Whether you say "0.13-micron" as most of us do, or "130-nanometer" as PR flacks prefer, the phrase is weighing heavily on both Intel's and AMD's minds.

    Egads! It's the son of Jon Katz.

    1. Re:it's a bird, it's a plane... by mrfiddlehead · · Score: 1
      Mod this up. Damn that's the funniest thing I've read all day.

      BTW, most of us (the rest of the world) prefer nanometre. Personally I prefer the attoparsec.

      --
      :wq
    2. Re:it's a bird, it's a plane... by Anonymous Coward · · Score: 0

      Yeah, it was intended as a joke. I started reading the summary and thought to myself, "Ahhh! Another dose of Katz's top-notch journalism", then I noticed it wasn't him at all. I was half expecting it to continue on as "In Germany they call it 'nanometrikingerung', in France they say 'nanometrois', and in most of Central and South America they say 'el ninometre'."

      *shrugs*

  13. Those PR drones.. by TeknoHog · · Score: 0, Offtopic

    will probaly bastardize that one too. Nanons it must be, by the same non-logic. That'll even make it sound less metric.

    --
    Escher was the first MC and Giger invented the HR department.
  14. Rule: Fast CPUs make life good by Anarchofascist · · Score: 1
    A couple of things a fast CPU can be good for:
    • Real-time rendering of fractal worlds
    • Compiling
    • Fast simulations
    • Resurrecting interpreted languages (like Java)
    • Emulators! Mame! X64!
    • Excellent screen savers
    • Flash
    • Discreet simulation
    • Particle systems
    Although, you're right, there are a lot of applications out there nowadays that don't run any faster with a faster processor. Witness all the absoute crap that Intel is pushing in it's ads about increasing Internet speeds. However, just because there are many programs that don't improve their performance if you buy a high-end graphics card, high speed ethernet card, or wireless networking card, but that doesn't mean that these cards aren't cool or interesting. I bet there are many more non-game programs that perform better with double the CPU speed than there are that perform better with double the polygon rate.

    So.. short version: Leave Santa's factory alone! I want neat toys, and 2 GHz processors are definitely on the list!

    --
    Once more unto the breach, dear friends, once more, Or close the wall up with our American dead!
  15. Re:Ripoff by Anonymous Coward · · Score: 1, Funny

    Perhaps those who submit comments should come up with their own blurbs, rather than plagiarizing the first paragraph of whatever they're replying to.

  16. My Packard Bell P75 by Knunov · · Score: 2, Insightful

    I bought my first computer in 1995. It was a Packard Bell P75.

    Go ahead. Laugh. If you told me you actually paid money for a PB, I'd laugh, too.

    PB actually used good motherboards in their systems. It was the components that sucked.

    Anyway, to this day, I *still* have and use my PB computer. Yes, it went from a P75 -> P133 -> P200 MMX, and went from 8MB -> 32MB -> 64MB -> 128MB and the hard drive went from 1GB -> 4GB -> 20GB, but it's stll in use.

    Admittedly, I've bought other computers since and I no longer use it as my main machine, but I *could* if I wanted to. I only bought faster machines because I wanted to, not because I needed to.

    It runs Win98 like a charm and runs Linux even better. It has always been stable and still is, 6 years later.

    If people would cater to their needs instead of their wants, the CPU industry would either wither, or they would start offering REAL improvements. These 100MHz increases are BS.

    They need to start with a minimum 1GHz jump and better internal architecture. Everything else is just them going wallet fishing.

    Knunov

    --
    Why do users with IDs under 100,000 or over 700,000 usually have the most worthwhile comments?
    1. Re:My Packard Bell P75 by Anonymous Coward · · Score: 0
      Yes, it went from a P75 -> P133 -> P200 MMX, and went from 8MB -> 32MB -> 64MB -> 128MB and the hard drive went from 1GB -> 4GB -> 20GB, but it's stll in use.

      Luckily, that was before XP or you would have had to call in for 7 product activations ;)

    2. Re:My Packard Bell P75 by Ace+Rimmer · · Score: 1

      Yes, I can still edit my project's source in vim as I could with my old P133 but I dislike waiting (about) 12minutes to compile the affected subtree
      instead of 2 minutes on my Athlon.

      Yes, I'm impatient ;)

      --

      :wq

    3. Re:My Packard Bell P75 by colatek · · Score: 1

      I am not going to laugh. I bought a PB 75 too. My niece is using it today. Never a problem with the thing. I now own a Mac. OS X rocks! :)

    4. Re:My Packard Bell P75 by Henriok · · Score: 1

      Well.. I have Power Mac 7500. Originaly a 100 MHz computer.. but now it has a 400 MHz G4-processor, a USB/FireWire-card, twin 9 GB SCSI-drives, two graphics adapters and a 10/100 ethernet-adapters (and of cource the standard 10 Mbps internal). And.. 512 MB RAM. It runs Mac OS X just perfectly, and Linux, and BeOS and Mac OS 9.. bought in the fall 1995.

      Got to love those Macs.. quite upgradable.. who'd known? And a PCI-slot to spare..

      --

      - Henrik

      - when the Shadows descend -
  17. No way, I'm supersticious. by snatchitup · · Score: 5, Funny

    No friggen way I'll ever own a 13 nanoM chip. I'm just too supersticious. I've got enough to worry about with my data, and (jpg)'s to trust them to an unlucky number. It's worse than a hat on the bed!

    They should switch to Angstroms.

    Oh wait a minute, my calculator tells me that 0.13 Microns equals 666 Angstroms. Holy Ess, The end is Nigh.

  18. It didn't help VIA/Cyrix. by Penguinoflight · · Score: 1

    While 0.13 micron/130 nanometer will help the heat on these chips, VIA has had 0.13 micron chips for about 6 months, and their sales aren't to great :-)
    While we'd like a 0.13 micron chip (that's faster than 700mhz), a lot of people don't know what a micron is, and they're the ones buying P4's.

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
  19. I noticed Hammer has been moved back by shimmin · · Score: 1
    AMD's previous roadmap had the ClawHammer's debut in 2H 2002, while the new one has it stradding 2H 2002 - 1H 2003, with the multiprocessor versions definitely not coming out until 2003.

    Does this indicate unanticipated troubles with x86-64?

  20. No... by 13Echo · · Score: 1

    "But don't you get a thrill out of the fact that you nearly have more processing power on your desktop than the entire world did twenty years ago?"

    No, because some of us get laid.

  21. CPU speed Nuts... by oconnorcjo · · Score: 2

    I just don't get the desire for machines faster than 600 mghz. The CPU is going at least twice as fast as any other component on a PC machine. What I did recently was buy a DDR motherboard to get ram that ran at 133 mghz (advertised at 266 mghz) and so I got a AMD 1.4 gigahertz cpu with it. One of the nice features of the motherboard was the ability to change the clock rate of cpu and bus. I LOWERED the clock rate of my CPU to 800 mghz and my machine is as responsive as I would ever want it to be. When I hear that Intel is charging twice the price for thier 2.0 gigahertz CPU as thier 1.8 ghz and people go out in droves to buy the 2 ghz anyway boggles me! Most of them don't need the speed of either CPU AND people are willing to pay 100% more money for a measly 10% performance boost. Ten years ago, Most PC's came with a "turbo button" on the case with the idea that only when you really had to use the the cycles would you press turbo and the CPU would go twice as fast. Back then, the button was pointless because when computers were going at 66 mgz, processors would regularly be very busy. But today the Turbo Button would actually be a nice feature. When doing word-processing or surfing the web, have the machine go slow but then when playing quake 18 (Revenge of the killer CPU), press the turbo button so the bloatware can look sweet. However, for people who REALLY NEED more power (all of the time) *couph* *couph*... SMP looks to be the far better alternative than these monster single cpu solutions.

    --
    I miss the Karma Whores.
    1. Re:CPU speed Nuts... by Ace+Rimmer · · Score: 1

      The turbo button defaulted to ON. You could switch it off if you wanted to play old bad designed game which would be unplayably fast ;-)

      --

      :wq

    2. Re:CPU speed Nuts... by Anonymous Coward · · Score: 0

      uhm no. the turbo was there so you could drop the clock to 8 mhz and be able to see all your old games (like frogger).

    3. Re:CPU speed Nuts... by ivan256 · · Score: 2

      Let me guess, you slowed the chip down to 800 Mhz just so you could tell everyone that you don't need such a fast machine, and that they dont need it either. You're just like one of those obnoxious people that feels the need to tell everybody that they don't have a TV, like that makes them better then you or something.

      If you have the speed you might as well use it.

      Also you may have lowered the stability of your machine by slowing it down that much. Certain parts of the logic need to 'refresh' to maintain their state, and when the designer assumes that the minimum speed a CPU will be sold at is 1.something Ghz, they might not make sure the charge sticks around long enough to work at less then half of the intended clock speed. But you're so smart...

    4. Re:CPU speed Nuts... by CTho9305 · · Score: 1

      I LOWERED the clock rate of my CPU to 800 mghz and my machine is as responsive as I would ever want it to be.

      ooh, special. OBVIOUSLY windows doesn't need more than that... XP is indistinguishable between my roomie's tbird 1.4 and my tbird 700. However... fire up some UT. His framerates are always over 60 (as in, smooth), whereas mine drop down to about 45 sometimes. Same video card. So, why don't you do some tests like that? While you're at it, find a high polygon demo like the one in 3dmark2k1, and compare the smoothness. YOU NEED a fast cpu to come even close to smoothness.

      Regarding clock throttling... K6-2+ and K6-3+ can do it, and hopefully standard modern processors will too. However, since they don't why not let your CPU do something productive with those idle cycles?

      However, for people who REALLY NEED more power (all of the time) *couph* *couph*... SMP looks to be the far better alternative than these monster single cpu solutions.

      SMP requires multi-threaded apps for any benefit.

      and... it is MHz, not mghz. cough is spelled with a g.

    5. Re:CPU speed Nuts... by CTho9305 · · Score: 1

      Oh, last night I was playing around with fans... and incredibly, everything is responsive underclocked to 500MHz, running fanless :-)

      oh wait, my 3d studio max rendering took WAY too long. it is noticeably faster at a higher clock speed.

    6. Re:CPU speed Nuts... by jkavanau · · Score: 1

      For most applications and uses you are perfectly correct that most people don't need more than 600Mhz or so. However for the gamers out there the increased cpu speed does help, just check out benchmarks on someplace like sharkyextreme.com. The same system with a faster CPU gets faster FPS, of course the FPS it is getting are well beyond anything that matters. Scientific modeling and high-end graphics work is really where these cpus come in handy. Even though they are running at those immense speed, remember that some x86 instructions take 4 cycles to complete, some might take more, don't have my reference handy, the inefficiency of x86 helps even out the fact the cpu runs faster than everything else I guess...

    7. Re:CPU speed Nuts... by Anonymous Coward · · Score: 0

      You are so right..
      SMP is a much nicer way to go...

    8. Re:CPU speed Nuts... by LoonXTall · · Score: 1

      "His framerates are always over 60 (as in, smooth), whereas mine drop down to about 45 sometimes. [snip] YOU NEED a fast cpu to come even close to smoothness."

      News flash: PAL framerate is 25 fps. Even the blazingly fast NTSC framerate is only 30 fps. You're claiming 45 isn't smooth, yet I've never heard anyone complain about the smoothness of television....

      --

      ~~~LXT~~~
      Life is like a computer program: anything that can't happen, will.

    9. Re:CPU speed Nuts... by Mr.+Piccolo · · Score: 1

      Yeah, but nobody said the two interlaced images had to be for the same moment at time either. IOW the effective framerate for PAL can be 50 FPS and 60FPS for NTSC.

      30FPS in video games isn't smooth for me.

      --
      Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
    10. Re:CPU speed Nuts... by oconnorcjo · · Score: 2
      Also you may have lowered the stability of your machine by slowing it down that much. Certain parts of the logic need to 'refresh' to maintain their state, and when the designer assumes that the minimum speed a CPU will be sold at is 1.something Ghz, they might not make sure the charge sticks around long enough to work at less then half of the intended clock speed.

      Actually, I underclocked my machine because I was trying to insure stability (not that I had any anyway but then it never hurt). I am told that a lot of servers are underclocked for the same purpose. I also had the idea that my cpu would run cooler thus reducing any chances of overheating and at the same time saving electricity since I keep my main machine on 24/7. As for instability, I have had none of that and I would not expect to. That is usually an OVER CLOCKER problem (which I believe AMD and Intel do which is indicated by the need for huge heat sinks and fans).

      --
      I miss the Karma Whores.
    11. Re:CPU speed Nuts... by ivan256 · · Score: 2

      Underclocking may increase stability in small doses. 10% is probably fine, but I have worked with CPUs in the past that don't work as documented when underclocked more then 25%. Don't trust your data with an asumption. Manufacturers publish specs for a reason.

  22. war by VEGETA_GT · · Score: 2, Insightful

    Well to be honest, I have been watching this sine the first Athlons came out and proved that Pentium was not all that. So far AMD has been able to bask down Intel at every turn. The 2 ghz p4 is still slower then amd's athlon 1900 (1.6 GHz). Its not the speed, its what you can do per clock cycle, and amd chips dose do a lot more.

    But reading the article, I find that the again go after the ghz number,

    Of these, the P4 Northwood could be the most compelling CPU release of 2002

    Their reasoning, the p4 well be unto the 4 GHz barrier in a few months. The Athlon is planning to make some jumps as well which, makes this sounds to me like the article is written by someone leaning towards the users who love big GHz numbers and not real speed.

    What makes this even funnier is the fact that most users could buy a 1 GHz and still play the latest games and the other things in 2 or 3 years.

    my 2 cents plus 2 more

  23. CPU is not problem anymore by El_Nofx · · Score: 3, Insightful

    Unless you are ripping Divx movies left and right or a Seti@home freak you don't need a faster cpu, It will do nothing for you. Anyone notice that you pretty much have the same Harddrive as you did with your pentium 1 120, the size has increased but if you go IDE it is still 7200rpm and the data transfer rate isn't any faster.
    It is funny, Xp Pro runs the exact same on my PII 400 with 384 meg of ram as it does on my PIII dual 1 gig with a gig of ram machine. The 400 actually boots faster!. So what does processor speed to for you in every day apps? everyone here knows exactly what i am saying. I am just complaining becaue we always hear about the new processor that is supposed to be so great that is coming out next year or whatever. WHEN AM I GOING TO SEE A SOLID STATE HARD DRIVE? Sure Serial ATA is coming up but the transfer rate on that is only starting at 166MB/s. ok. show me a harddrive that actually needs anything better than ata 100 first.
    The bottleneck in every modern computer is still the hd, and the bus, we should fix those first and then jack up the mhz..

    --
    It's not the OS it's the user that sucks. If it's user friendly, you get stupider people. - clinko
    1. Re:CPU is not problem anymore by elflord · · Score: 1
      Unless you are ripping Divx movies left and right or a Seti@home freak you don't need a faster cpu, It will do nothing for you.

      I do a lot of compiling, and write numerical analysis software. Both my athlons get plenty of use. But you make a good point-- most people just don't need it.

      Anyone notice that you pretty much have the same Harddrive as you did with your pentium 1 120, the size has increased but if you go IDE it is still 7200rpm and the data transfer rate isn't any faster.

      The drive in my Pentium 133 was not 7200 rpm. Also, IDE technology has improved since the Pentium I days. And the new drives are much quieter. For the same noise and cost as an old IDE drive, one could get a SCSI disk at 15k RPM nowadays.

    2. Re:CPU is not problem anymore by CTho9305 · · Score: 1

      Ever compiled a linux kernel? Done 3d rendering? I do some 3d stuff (just for entertainment, pretty crappy stuff but the rendering is much faster on faster computers.

    3. Re:CPU is not problem anymore by CTho9305 · · Score: 1

      Ever done any 3d work? I do some pretty crappy stuff but faster processors = faster render time. Same with compiling stuff.

      However, I definitely agree with you about improving hard drive / memory

    4. Re:CPU is not problem anymore by NoMoreNicksLeft · · Score: 1

      Actually, I'm moving up to fibre channel with software raid 5. I fully expect to be able to a constant data transfer of over 100mps. I'm afraid I won't be using XP though.

      Maybe if you dumbass consumers weren't busy jerking off to the latest IDE spec, you'd have noticed 2 or 3 alternative technologies that are quite a bit faster.

    5. Re:CPU is not problem anymore by NerveGas · · Score: 2

      Unless you are ripping Divx movies left and right or a Seti@home freak you don't need a faster cpu

      Actually, these MHz wars benefit me in a very nice way. I'm still using a PIII-650 at home, but my servers have much more substantial hardware - dual CPU's are the *smallest* machines in the stack. And these MHz wars have made desktop machines that can best high-end servers of only two years ago.

      Two years ago, I spent $4,000 on a chassis and motherboard that would use quad Xeons. Add in $2800 for the processors, and that's a lot of money. Today, I can spend $200 on a dual Athlon motherboard and $500 on two chips, and have a machine that will either rival the quad Xeon or beat it in almost any situation.

      I remember when I was amazed that opening up an 800x600 JPEG took less than three seconds on a new machine. The funny thing is, at the time, I didn't mind waiting three seconds, and really hadn't even noticed that it was a wait. But once I'd used a faster chip, going back to the three-second wait really cramped. Even though you don't *need* a faster procesor, chances are that the next time you upgrade, you'll start noticing little things like that, and say "Wow... this is nice."

      As an interesting side note, if you're looking for longevity out of a computer, go dual CPU's. I had a dual Pentium-133 w/ 64 megs sitting around that I bought for $40. For fun, I put NT4 on it, and in nearly every situation, it was almost or more responsive than a P3-650 with Windows 98. Yes, computationally-bound processes took a while, but in sheer responsiveness, it really impressed me. I think that a dual 1.6 GHz Athlon would have a tremendously long usable life span.

      steve

      --
      Oh, you're not stuck, you're just unable to let go of the onion rings.
    6. Re:CPU is not problem anymore by Spl0it · · Score: 1

      Ever since AMD released their K6-2 chip with 3dNOW, the market has been gradually and consistantly moving in their favour! Yes, intel has higher mhz chips, but they all run slower, maybe the reason why your p2 400 and p3 dual 1gig don't run much different is because frankly the one is just faster mhz, and nothing more? eh? look at the comparisons between amd and intel intel has faster mhz amd has slower mhz intel's chips cost more and's chips cost less amd's chip still run faster and do more per cycle then intel therefore AMD > Intel.. I'll never buy intel again after that wonderfull k6-2 :)

      --

      No, this is
    7. Re:CPU is not problem anymore by Explo · · Score: 1

      It is funny, Xp Pro runs the exact same on my PII 400 with 384 meg of ram as it does on my PIII dual 1 gig with a gig of ram machine. The 400 actually boots faster!. So what does processor speed to for you in every day apps?


      Yeah, Mozilla surely works as nicely on PII 400 as on TB 1200 :P While it's a quite heavy and non-typical example of a normal application, it's definitely not the only program that feels hell lot of faster. Besides, who said that I want to use 'everyday' applications? I like my compilations to go fast, thank you...

      --
      Everyone who makes generalizations should be shot.
    8. Re:CPU is not problem anymore by Anonymous Coward · · Score: 0

      Of course CPU is still a problem. It's not the only problem, but then, it never has been.
      I do a lot of 3D rendering, manipulation of hires graphics, and sound processing (virtual analog synth type stuff), so I need all the CPU I can get. I could actually *use* a processor 10 or 100 times as fast as my current one (600MHz) easily.

  24. AMD Link by base2op · · Score: 1

    Anyone else notice that MSOfficesque error on the AMD link? Where it says "ClawHammer". I just thought that was funny.

  25. Half a mil? Isn't that a bit large? by Anonymous Coward · · Score: 0

    A mil is 1/1000 of an inch. Let's see, at 2.54 cm/in, that gives us 25400 um per 1000 mils, or 25.4 um/mil. Half a mil would still be about 13 microns. So you're off by a factor of 100.

    Even if you were under the mistaken idea that a mil is one millionth of an inch, you're wrong, because now half a mil would be .013 microns, off by a factor of 10.

    Sorry to be so pedantic, but your "Guess nobody knows what a mil is" was just a bit too snotty to not get a smackdown.

  26. Re:Half a mil? Isn't that a bit large? by Anonymous Coward · · Score: 0

    A mil is a millimetre. Join the metric revolution.

  27. A matter of time by Anonymous Coward · · Score: 0

    The idea is simple: though an Athlon can do more per clock cylcle than a Pentium4, Pentium4's clock frequency is going to increase faster than Athlon's. Thats what they're designed for... At a given time (in the near future I believe) the fastest Pentium4 avaliable will outperform the fastest Athlon available.
    The big question for now is "How long will that situation last, before the Hammers get out?" The longer it lasts, the more it will hurt AMD. These recent delayings in AMD's roadmap don't look too good.

  28. Stop the train! by niekze · · Score: 3, Interesting

    Am I the only one who notices that every week /. posts a news article about Intel or someone coming up with supar-dupar-mega-fantabulous technology that we never hear about again?

    Like New Optical DSPs With Tera-ops Performanc
    Or Intel Cites Breakthrough In Transistor Design
    Perhaps Clockless Chips
    Not forgetting Intel Promises A Cool Billion (Transistors)
    Notwithstanding Intel Claims Smallest, Fastest Transistor
    But who could forget Intel Claims 10Ghz Transistor
    Which looks a lot like Intel Says 10GHz By 2005
    But is just as vapor as Intel Creates 30-Nanometer Transistors
    or my personal favorite: Intel Goes for Display Encryption

    How can they get any work done when they're too busy telling us what they predict in a bajillion years?

    --


    Chaos, Mayhem, and Destruction: Not
  29. Re:Fast CPUs might be good - here's why. :) by Anonymous Coward · · Score: 0

    With linux there has been little change in real performance since the P1-150. My machines run dual PPro 200's - very snappy for code editing and other interactive tasks, and dirt cheap. I keep a dual-533 PIII for occasional heavy number crunching. The BEST thing about ultra-fast CPU's is that they drive the prices WAAAAY down on perfectly good machines built 3-5 years ago. Go eBay!

    bkr

  30. Could faster processors lead to better programs? by entrox · · Score: 4, Interesting

    I'm looking forward to ever-increasing clockspeeds, as this could get us away from programming applications in a low-level language like C/C++. Let's face it: Most of the bugs in current programs stem from the fact that C was not designed to handle sloppy or lazy coding. Dangling pointers, buffer overflows, memory leaks etc. result from the low-levelness of C (that's OK - for it to be efficient it needs to have the ability to do all kinds of things with the hardware directly). C should only be used for developing operating system kernels and device drivers, as no other higher language would handle the task well.

    Faster processors and more memory would make higher languages such as Lisp or Python viable for applications (such as Browsers, Desktop environments etc.), which in turn would result in less bugs and increased stability when applied correctly. The current state with software makes me sick. I don't blame it on C per se, but on programmers using the wrong tool for the wrong job.

    Writing in such a higher language would probably even increase portability (which C can't fulfill by a far shot) as you would program at a higher abstraction level. No need for autoconf/automake or ugly defines scattered throughout the code, making maintainance more difficult.

    I hope that more coders switch to some better suited language than C/C++ for application development. I've switched to Lisp myself.

    --
    -- The plural of 'anecdote' is not 'data'.
  31. The Pentium 4 is now just a puppy with big feet. by Futurepower(tm) · · Score: 3, Insightful


    I consider the Northwood to be the "real" Pentium 4, just as other second-generation products like the 100MHz Pentium and "Coppermine" Pentium III have proven to be the "real" versions of Intel processors in the past.

    I agree with this. The Pentium 4s we see today are just puppies with very big feet. They will grow up and become something much more impressive.

    --
    Bush's education improvements were
  32. Re:Fast CPUs might be bad - JAVA!!!! by Anonymous Coward · · Score: 0

    Not bad at all... Programs in OO languages (e.g.Java) will be a lot faster. Plus, combined with the short development time of these OO languages, and the relative ease in creating new products, games (and other apps) will cost a lot less to the consumer. $15 for a quality 3-d game (e.g., REturn to Wolfenstein?) vs. $40.

    In my opinion, it's a lot more productive to create software that maybe huge, but written in 15% of the time than to try to squeeze the hell out of a C/C++ program. In addition, if a 6ghz processors will run the "bloated" programm 99.99% as fast as the unbloated program, I'm up for developing the "bloated" program.

    This is seems to be the same argument with assembly and c/c++ 10 years ago!!! Ie., if you wanted to write a serious app (especially, 3-d programs), you would write c/c++ code that had inline assembly. Now a day nobody really cares for assem. People try to avoid it even though programs written in assem are smaller and faster :-) Obviously, development would be a bitch in terms of time and resources.

    Khamla Savathphoune

  33. Will this help Redhat Bloatware? by renehollan · · Score: 2
    Yeah that was a bit of a troll.

    I'm currently awaiting my first new PC in a long-time: Soyo Dragon+ mobo, AMD Athlon XP 1600+ with 512 MB DDR RAM, ATA/100 WD 100GB disk (yes, /me likes SCSI, but likes $$$ more), generic DVDROM, and Netstream2000 H/W MPEG2 board. In preparation of it's arrival I downloaded a copy of Red Hat Linux 7.2 with the intention of installing it on an old spare 1.5 GB drive I had free in my old, ailing PC (Intel P200, 80 MB RAM), just to give it a whirl.

    Well, things were real tight with the small drive, and my on-board IDE controllers were acting flaky anyway, so I ended up getting a "spare" 20 GB ATA/100 Maxtor drive and Maxtor (re-labeled Promise) ATA/100 PCI controller. The 20 GB Maxtor was now UDAM5 hde on ide2.

    The point of all this history is to illustrate that I now have a "soon to be spare" computer where the limiting factor is CPU and to a lesser extent RAM. I go ahead an install RH Linux 7.2 on the new drive.

    After a bit of farkling around with kernel boot options (ide2=d000,c802 is your friend!) I boot into RH Linux 7.2, in all it's X 4.0.1 glory.

    .... and it struck me as slower than RH 6.2 on the same box, running from a slower drive on a slower, flaky mobo IDE interface (prolly not even ATA/33). Not much slower, but slower nevertheless.

    I'm fairly sure that the new box would make the speed difference between RH 6.2 and 7.2 imperceptible, but the experience left me wondering about the extent of bloat in RH Linux releases, not that I'd want to run anything significant on the P200 anymore, but I might want to use it as some type of low-duty server, with an up-to-date kernel. In a nutshell, what got slower?

    No doubt, the new machine will be welcome.

    --
    You could've hired me.
    1. Re:Will this help Redhat Bloatware? by Shabazz · · Score: 1

      You're absolutely right. I recently did a clean install of RH7.2 on my Athlon 700 and it runs significantly slower than Win2k on the same machine. And to rub it in even more, I'm letting Linux run on a 10000RPM IBM UWSCSI drive while Win2k is relegated to a 5400RPM IDE drive that isn't even working in DMA because of driver issues.

      I've been using linux since '95 and I am amazed at the fact that it runs so slowly now. I'm sure there are things I could do to speed it up. But that won't change the fact that Win2k smokes it on lesser hardware. Woe is me. I wish things were different.

    2. Re:Will this help Redhat Bloatware? by renehollan · · Score: 2
      Point noted, except you're comparing apples to oranges and I compared apples to apples.

      In my case, unless I'm doing some long-term processing, the key isn't "fastest", but rather fast enough. I wouldn't spend much $$$ to get a kernel build down to 30 seconds from a minute, for example -- a minute is fine for me for the few times that I build a kernel. 30 minutes, of course, is annoying.

      --
      You could've hired me.
    3. Re:Will this help Redhat Bloatware? by Shabazz · · Score: 2, Insightful

      I was just giving another example. RH6.2 on my computer was faster than Win98SE. I recently wiped everything and went Win2k, RH7.2 without changing any hardware.

      Everyone who wants to see Linux succeed on the desktop (including myself) needs to recognize that all those bad words people hurl at MS won't change the fact that Linux + XF4.0 runs significantly slower on the same hardware.

      A lot of the advantages of Linux on the desktop start to disappear when you realize that it takes a lot of power to run it. It's not agonizingly slow on my computer, but it's pretty frustrating. Especially when Win2k just hums along on a slower disk with an "inferior" interface.

    4. Re:Will this help Redhat Bloatware? by renehollan · · Score: 2
      A lot of the advantages of Linux on the desktop start to disappear when you realize that it takes a lot of power to run it.

      True enough. I remember the days, probably up to RH 6.2 when [GNU/]Linux distros were generally snappier than bloated Microsoft offerings, even as the user productivity apps were less mature. It would be a sad day indeed, when standard GUI and productivity apps available under a [GNU/]Linux distro were slower, just to get more features "out there" -- stick to the tried, true, and efficient, until the polished can compete with it's peers on performance.

      --
      You could've hired me.
  34. That PPC roadmap... by Anonymous Coward · · Score: 0

    ...gives no dates and no new information that wasn't already announced. It isn't really a 'roadmap' per se, as it is 'things we are envisioning for the future of the product line, but aren't going to give any definites that anyone can plan around'.

  35. CPU != today's bottleneck by prisonernumber7 · · Score: 1

    When it comes to newer, better and faster technologies even geeks happen to be the ones that throw away their knowledge against better knowledge and buy whatever shows the higher measure unit/product number/version count.

    It's a pity; whilst there is nothing wrong with spending your time to compile that new Linux kernel every three days or so, it is plain right stupid to scrap a 1400MHz cpu for, say, a 1800MHz cpu. The discrepancy in cost vs work efficiency is minimal in this example.

    I have asked myself the question: What advantage will a new CPU give me? Will it make that windowed os which I love so much boot faster? Will it make my email download faster? As funny as it sounds, that's what Intel is advertizing their p4 chips with in my country.

    When I now look at how I could possibly speed this already incredibly fast FreeBSD toy of mine even more, in terms of effective result, which steps do I need to take? First off, I need to get rid of this old and awkward IDE harddisk. Preferably I'd tune in a SCSI raid, with lots of cache on those harddisks. That would probably give me a serious advantage, probably the highest I could achieve this easily; though, that would be redudant, because my X starts in less than two seconds ( with enlightenment and gnome) when I start it the second time anyway.

    --
    && aemula C. ab stirpe interiit
  36. Cyrix and Transmeta by Anonymous Coward · · Score: 2, Informative

    Yawn. Another article purely pushing Intel's and AMD's chips going another notch in clock speed. In the meantime, Cyrix and Transmeta have both shipped CPUs based on new cores, the Cyrix one at .13 micron, and no one bothers to mention it.

    1. Re:Cyrix and Transmeta by Anonymous Coward · · Score: 0

      why don't you point us to the cyrix anouncment then?

      BTW Cyrix (at least in the 100 MHz days) blew ass berries with a loud fart followed by a stench that hung around for about 3 hours and a stain on the chair afterwards.

  37. Speed up Rest of System by Anonymous Coward · · Score: 0

    Faster CPUs fail to make computers more useful mainly because the rest of the system stays largely the same.
    User input is still max a few bytes a second because most people still use mouse and keyboard. Supporting more and bigger displays with more colours has been nice over the last few years, but connections between computers over the internet are not speeding up at anything like the rate at which processors are accelerating.

    Give us a neural interface and a fiber bundle into every home, and the nature of the beast will change.

  38. Please don't take it personally... by Anonymous Coward · · Score: 1, Insightful

    but I'm sick of this "C for kernel, bloatlang for everything else" BS. I'm writing a ALife sim of language evolution program (for my thesis) in C and I'm thinking about writing agent ai code in *asm*, because compiler generated code won't be fast enough. I wrote simple AI apps for fun, multivariable optimization programs and finite element solvers for modelling at work, ran sound and video editing programs and ALL could use some more optimization at a lower level. C, asm, fortran aren't going anywhere until compiler technology advances to the point that they can produce better code from a problem description than a human can.

    1. Re:Please don't take it personally... by Just+Some+Guy · · Score: 3, Insightful

      I'm thinking about writing agent ai code in *asm*, because compiler generated code won't be fast enough.

      You're in a position to write a thesis involving AI, so I assume that you already have a bachelor's in CompSci.

      Did you learn nothing from it?

      I mean, do you honestly believe that you can increase the speed of your programs enough by abandoning an easier-to-maintain language to make it worthwhile? What happens when the next generation of compilers comes around that's faster than your hand-tooled assembler, and you have to re-write your code yet again to squeeze out those extra cycles? What if your code gets executed on a modern processor with deep pipelining, advanced branch prediction, and out-of-order execution? Are you that confident that your manual re-write will take full advantage of the hardware it's running on, moreso than a computer-optimized version?

      I'm sorry, but unless your AI consists of a very few tightly-rolled loops that you can super-optimize, I just can't see the benefit of throwing away 30+ years of compiler design experience for a theoretical gain that may or may not appear.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:Please don't take it personally... by MarkusQ · · Score: 2
      by Anonymous Coward on 10:57 03 December 2001 (#2648773)

      but I'm sick of this "C for kernel, bloatlang for everything else" BS. I'm writing a ALife sim of language evolution program (for my thesis) in C and I'm thinking about writing agent ai code in *asm*, because compiler generated code won't be fast enough.

      I assume you registered at the university instead of attending as an "Anonymous Coward"--otherwise, the diploma isn't going to do you much good.

      -- MarkusQ

    3. Re:Please don't take it personally... by Anonymous Coward · · Score: 0
      You're in a position to write a thesis involving AI, so I assume that you already have a bachelor's in CompSci. Did you learn nothing from it?

      That assumption is wrong, my undergrad has nothing to do with compsci, but my master is cogs. Nevertheless I assume I know enough for undertaking such a project. Fell free to prove me wrong, I can only benefit.

      I'm sorry, but unless your AI consists of a very few tightly-rolled loops that you can super-optimize,

      Yeah, that's it. The AI implementation is basically an ANN, I know which computer it will run on (mine), I know no current compiler can use 3dnow!+ instructions effectively, I know 32bits precision is enough for me, I know how long will I have to maintain the code and I know the NN part of the code will be just a little part of the project but will be executed much more frequently than other parts. So optimizing three main loops for a -say- 40% reduction in execution time of those loops, I can realistically expect the whole simulation will speed up about 20-30%. All this information is not normally avaliable to an application developer, so perhaps my comments about assembly were off-topic, nevertheless the idea is sound and I'm not the moron you are thinking of. Hand coded parts will perhaps be less than 1% of the whole.

    4. Re:Please don't take it personally... by Just+Some+Guy · · Score: 2

      That assumption is wrong, my undergrad has nothing to do with compsci, but my master is cogs. Nevertheless I assume I know enough for undertaking such a project. Fell free to prove me wrong, I can only benefit.

      The issue that I see is that even a 40% performance increase is still well below what I would consider to be the threshold of useful optimization. I mean, that's less than one year's hardware progress. Sure, it may be tempting now, but wouldn't it be better to leave your research in a form that's more accessible to a large audience? Granted, C may not be the lingua franca of AI research, but I'd be willing to bet money that more AI researchers can read C than AMD assembler. Wouldn't you at least like to have the option to have your code peer-reviewed by researchers who don't know 3dnow?

      I'm not the moron you are thinking of.

      If you're implementing ANNs, then I'll give you the benefit of the doubt and assume that you're not. :) Still, I disagree with the conclusion you reached. The ability to maintain programs I wrote 6 months ago and share them with my colleagues is much more important, IMHO, than squeezing out every last bit of performance.

      --
      Dewey, what part of this looks like authorities should be involved?
    5. Re:Please don't take it personally... by Anonymous Coward · · Score: 0
      Actually, the primary issue is not performance. I have about 1.5 years to complete the project, programming &debugging perhaps will take more than 6 months of that time (unless I find some good Alife library. Something like turtles, rather than zeus or antfarm.) The research topic is not well understood, it is not clear under what conditions a syntactic language emerges from a population which have no initial bias for serial and symbolic processing and agent communication is not forced. That means I will fail and fail and fail and fail until I get the sim conditions just right so that I can draw a conclusion about possible prelinguistic community. Even if I succeed at the first try, in order to draw such a conclusion I'll try to find parameters that fail so that I can contrast with parameters that succeed. If I can't draw such a conclusion, I'll get no master's degree. So the issue at hand is constructing a framework in which I can test many different conditions. I can do this

      1 - By making the program faster

      2 - Completing the program earlier

      3- By finding more computing power.

      Option 3 is my first priority (the idle time of all PC labs look so juicy), 2 is second (a good lib will save me a lot time, but not optimizing will save very little), 1 is the last resort (that is the asm part.) I don't really care how fast it runs as long as I can complete my thesis. Oh, there is also a fourth option: Wish me luck.

    6. Re:Please don't take it personally... by mgblst · · Score: 1

      Dont listen to this guy, everybody knows that Assembly is the way of the future!!!!

  39. Re:Could faster processors lead to better programs by avsed · · Score: 1

    Unfortunately your wishes have already come true, and I (and many in industry) would draw the exact opposite conclusions you have done. Faster CPUs encourage laziness (which you seem to be advocating by claiming that C[++] is bad because it prohibits laziness - which in itself is not strictly true either). Laziness is bad; look at all the bloated, useless Visual Basic code out there. Business critical enterprise level software should almost never be written in a scripting langauge (even a good one, like Perl). Faster CPUs together with easily abused and easily learnt (at least to a basic level) scripting langauges produce undisciplined programmers . These, especially MS VB script hackers (in the correct, though non-complimentary sense of the term), are the scourge of the industry - churning out buggy, insecure, and monstrously inefficent code. That's not to say that all VB/Lisp/Perl is bad (I've seen good VB coders take bad production code and speed up business processes by orders of magnitude), just that every lanuage has its place and scripting languages are of little use for hard computing and business tasks.

  40. Re:Half a mil? Isn't that a bit large? by Anonymous Coward · · Score: 0

    No, a mil is not a millimeter. Leave it to some idiot to bring in side issues of incompatable systems of measurement. Check out the defenition over at m-w.com before you jump in with statements implying Americans are ignorant of the metric system. A mil is a number of things, but I don't see it listed as a standard abbreviation for millimeter. The third definition is the one to be used here, as microelectronics often use a mil as a unit of measurement in thin and thick film circuits, and hence it's relevance to die lithography.

    Anyone resorting to arguing semantics (what a mil is or is not; others arguing if micron is a valid abbreviation of micrometer, or micrometre, as the case may be) is often otherwise lacking in any meaningful argument. So do you all you lame-ass pedants have anything useful to contribute to this thread? Argh! Slashdot vexes me so!

  41. Did the 64-bit AMD technology slip? by Animats · · Score: 3, Informative
    The AMD roadmap shows their 64-bit CPU in late 2002. Is that a delay from previous announcements?

    That's too late. They need it sooner to compete with the Inanium.

    1. Re:Did the 64-bit AMD technology slip? by drinkypoo · · Score: 1
      That's too late. They need it sooner to compete with the Inanium.

      Considering the price point of AMD's cpus, I'm expecting it compete with Pentium IV, too.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  42. ehhh..looks cool by Aqua+OS+X · · Score: 1

    I hate to be the Mac geek around here... but whatever.

    Motorola tends to remain very vague about new PPC products to the public. They wait until they are actually in other vendors devices before the start to really talk about them. Motorola does this so other companies, like anal Apple, can have first dibs on telling the public about the new toys they are going to ship.

    If you hunt you actually can find interesting info on the G5. Variations of the "g5" have already begun to ship within certain routers, and as usual, a lot of Apple's hardware beta testers have been breaking their NDA and telling sites like The Register and MOSR what's in the beige test boxes.

    Who know s what this thing will really be like. But we know for sure now that it is 64/32bit, .13micron, uses moto's new SOI technology that came out a while ago, and was developed with a lot of "help" from Apple this time.

    Ya, this is very little info, but I do believe that this this is going to be quite sick. Obviously the G4 was a dud. It happens...hell, it did happen. Moto had an awful time trying to get the stupid CPU off the damn die, the thing didn't scale for beens, and it was seemingly aimed at bumping heads wit the last generation of CPUs. However now Apple has stepped in, the CPU seems to work well if you believe the rumors, moto seems to have a lot of buyers and potential buyers, they can actually produce and scale this next gen chip (thank god), yada yada yada. Moto and Apple have stepped back and collected their thoughts for a looooong time now. Apple/Moto practically skipped a generation (or half generation) of CPUs and motherboards. It makes sense that they would just come out with a product that is going to bump heads with hammer and itanium. They have had more development time since it didn't make sense to try and save the G4.

    god that was a big mac geek post...sorry ;)

    --
    "Things are more moderner than before- bigger, and yet smaller- it's computers-- San Dimas High School football RULES!"
  43. Re:Could faster processors lead to better programs by entrox · · Score: 1

    Don't confuse so called "scripting languages" with high-level languages. Lisp is by no means a scripting language and can be compiled to native machine code. Perhaps Python was a bad example, so substitute Java if you like.

    Further, I was not claiming that C prohibits laziness - It's just that laziness can produce disastrous result (buffer overflows are a good example). Laziness when writing code is _generally_ bad and should be tackled more.

    You raise some valid points, but I'd prefer a little slower, but more stable and bugfree program over an slightly faster, instable and probably insecure one.

    --
    -- The plural of 'anecdote' is not 'data'.
  44. Re:Half a mil? Isn't that a bit large? by Anonymous Coward · · Score: 0

    Why persist in coming here, if it vexes you?

    Anyway, I worked in a machine shop for 4 years making bits of aeroplanes. A mil was a millimetre and a thou was a thousandth of an inch. It may be UK colloquialism, but I speak from my experience, not from a definition.

  45. it's cooler by geekoid · · Score: 2

    I have a 1.4 MgHz chip. thats plenty fast. the reason I want .13 is so it will run cooler

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    1. Re:it's cooler by msaavedra · · Score: 2

      I agree wholeheartedly with that sentiment. Unfortunately, I have a feeling the chipmakers plan on bumping up the clock speed to the point that the chips run just as hot. I personally would rather have a 1 GHz chip that dissipates 10 watts than a 2GHz chip that dissipates 70. I don't think these new chips will be available at 1GHz, though.

      --
      "Any fool can make a rule, and any fool will mind it."
      --Henry David Thoreau
  46. Re:Could faster processors lead to better programs by geekoid · · Score: 2

    personally I would rether drum all the sloppy and lazy coders out of the business.
    screw ease of programming and code readability. I want someone who is smart enough to figure it out to be coding, not some high level coder wanna-be.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  47. Re:Could faster processors lead to better programs by entrox · · Score: 1

    True, but I guess this doesn't work in the real world. Just compile the latest mozilla (or any 50% of open source "projects") and count the warnings the compiler emits. These are possible pitfalls the compiler detected, but there are certainly enough others which didn't get detected and can someday bite somebody.

    This happened to me: the latest mozilla would crash on me randomly and take the whole Xserver with it. I doubt something like that would happen, if it was written in some higher language (and properly designed).

    But you're right, it's not really the languages fault - it's the coders. As much as I'd want everyone to be disciplined and smart enough to figure it out, real world sadly doesn't work like this.

    --
    -- The plural of 'anecdote' is not 'data'.
  48. It is all karma by Anonymous Coward · · Score: 0

    Had I posted it with my account, it would have been marked as "troll" or "flamebait" or I would have to watch my tongue. Now it is posted as AC, and it even gets an "insightful" rating. The same with this message too, (almost) nobody bothers to mark an AC "Offtopic" unless it is a "FP"

  49. Already happened... by srvivn21 · · Score: 2

    Look at the transition from processor specific assembly to (possibly portable) C code. (Were computers not originally programmed with direct binary instructions?) More software is being written in interpretive languages (such as Perl and Java) than ever before. The transition you are asking for is occuring, whether you realize it or not. It has been occurring since computers came to be.

  50. AMD will announce 15 NanoMeter tomorrow at IED by bstadil · · Score: 1

    AMD will create the fastest switching speeds in the industry, the company claimed today. The CMOS (complementary metal oxide semiconductor) transistor has a gate length of .015 microns and AMD said the design will be a prototype for future generations of CPU it contemplates. And the invention will make for a 20-fold increase in the number of transistors per chip and a 10-fold performance bump in CPU speeds by 2010, claimed AMD. The 15 nm prototype device will be a key factor in the development of 30 nanometer (.03 micron) process technology which AMD said will be out by 2009 and use 12-inch (300 mm)silicon wafers. Craig Sander, VP of AMD's tech development group, said the 15-nm transistor is .8 volt device which will work at 3.33 trillion switches per second. AMD said it will release further details of its invention at the International Electron Devices Meeting tomorrow.

    --
    Help fight continental drift.
  51. Re:Half a mil? Isn't that a bit large? by Dahan · · Score: 1
    Isn't the point of language to communicate with others? If "mil" means mm in the machine shop you worked at, use it at the machine shop. But when addressing the /. populace, use the widely-accepted definition. Don't know what the widely-accepted definition is? That's what a dictionary is for.

    Anyways, the only definition of "mil" as a unit of length that I've heard of is 1/1000 of an inch.

  52. Stop all ready!!!!! by Anonymous Coward · · Score: 0

    Enough with your damn Solid state Hard drive!!!!!!!!!! you are driving us all nuts with your retarded dream. I am sure SSHD will come but stop whining about it.....do somthing about it.....you act like there is some conspericy to stop a SSHD from being created......got news for you.....you won't see it until they can perfect and create and affordable Holographic storage system. that will have the most density and least search/access time out of any SRAM soulution you can imagine.
    so.......

    SHUT THE FUCK UP!!!!!!!!

  53. Yeah! Ultra 160 SCSI or IDE raid! by zerofoo · · Score: 1

    I ditched my ATA 100 hard drive for an adaptec 39160 and a 35GB 10k rpm hard drive, that made a huge difference!

    I'm contemplating installing my Adaptec 2400A IDE raid controller with some 100 GB ATA 100 hard drives in raid 5 config....that will be even better.

    My last 3 CPU upgrades didn't impact performance as much as the disks did.

    -ted

  54. Intel ads on slashdot? by blair1q · · Score: 2

    Should I be surprised that I've never noticed the P4 ads until I saw the one popping up at the top of this thread?

    --Blair

  55. Tualatin PIII and Celeron 1.2Ghz? by Anonymous Coward · · Score: 0

    They are already shippping at .13 micron.

  56. you say potato by stud9920 · · Score: 1

    No, it's european for what you call billion. What we call a billion is a million millions (what you call a trillion). What we call a trillion in turn is a million billions (what you call a quintillion). I guess you gun carrying republican voting (or not voting) anti abortion pro death penalty hamburger eater get the idea.

    What we call a milliard is a thousand millions, what we call a billiard is a thousand billions, what we call a trilliard is a thousand trillions and so on. This is perfect English, but also works in French, Italian, Dutch and many others.

  57. Premature optimization by Convergence · · Score: 2

    Premature optimization is the root of all evil. I also was considering making the same types of choices you are looking at.

    My code deals with building massive 3d arrays containing tens of millions of cells and manipulating them. Obviously, the inner loops of the manipulation would be the bottleneck.

    So I ran my trusty profiler.... And found out that 90% of my time was being spent READING THE DATA IN.

    It took two lines of code to make that three times faster, making my program 2.5x faster.

    Interesting... Then, a couple of weeks later, I took a large deployed system with an active developer community, www.squeak.org, and ran that through a profiler, and found out how changing one line of code lead to 4% speedup in the core intererpreter, and lead to other simple changes that were just as valuable. I also ran the benchmarking in the interpreter, and sped up syntax hilighting by 40%.

    If I was doing something like what you were, I'd probably go all-out at using a more dynamic language (Smalltalk) for the extreme flexibility.

    Only devolve into C/assembly for the critical parts.

    Many times, the bottlenecks aren't where you think or might predict they are. Why spend weeks guessing incorrectly and optimizing code that won't help you go faster when the profiler will tell you exactly what magic bits to re-examine.

    It can also find O(n^2) artifacts and all the rest.

    If your code is currently running, run it through gprof and see where the CPU time is really going.

  58. Your personal favorite by Convergence · · Score: 2

    The display encryption idea from intel, that is the much ballyhooed HDCP, that was the subject of Niels Ferguson a few months ago. (also on slashdot), and one week ago, slashdot posted a news story announcing that it is completely broken.

    BTW, its not vapor, Apparently, a ten thousand bux 42 inch rear-projection TV from JVC actually is using the piece of digital control crap.

  59. Re:Half a mil? Isn't that a bit large? by Anonymous Coward · · Score: 0

    A mil?
    That's easy -- as a volume it's 1ml (or 1 cubic centemetre, if you prefer); as a measurement it's 1 milimetre.

    So 568 "mils" is a pint, and 304 "mils" is a foot.

    You really do have to like the english language for being so damn complex...

  60. Re:Could faster processors lead to better programs by benedict · · Score: 2

    On the contrary, laziness is one of the three chief virtues of a programmer.

    It's especially good when it keeps them from writing code in the first place ... less code means fewer bugs!

    --
    Ben "You have your mind on computers, it seems."
  61. Re:Could faster processors lead to better programs by benedict · · Score: 2

    C is *so* not a cure for laziness. Some of the most lazy and careless code I've ever seen has been C.

    It could be argued that a language that lets you express yourself tersely is less prone to laziness problems. If there aren't a million t's to cross and i's to dot, then there's no way to have a million uncrossed t's and undotted i's laying around at the end of the day.

    --
    Ben "You have your mind on computers, it seems."
  62. Hey, be nice to MIDI! by cduffy · · Score: 1

    There's no relationship between using MIDI and being behind the times -- none at all.

    I've invested a significant chunk of money in music equipment, and MIDI is the protocol that controls it. Listening to ".midis" doesn't need to mean cheap FM synthesis; rather, anyone playing a modern synthesizer is using it implicitly (as these systems frequently use MIDI internally to describe commands from the keyboard/foot pedals/etc to the synth module), and if a keyboard player records his instrument's data stream the same .midi files that you consider backwards can be literally the same as what the performer played on his synth.

    Okay, rant over... just be nice to MIDI... mmm-kay? :)

  63. Where is the app. to use with these speedy chips? by HuangHuang · · Score: 1
    I have one 600MHz computer at home. It is still working without any delay.

    So, why do I need these speedy chips?

  64. Re:The Pentium 4 is now just a puppy with big feet by screwtheNSA · · Score: 1

    Finally; a person that "sees" what the P4 WILL become and not what it is currently(WHEW). With so many "experts" touting how a change from 1.2 Ghz to 2.2 Ghz will make XXX run faster, how about better, Hmmm? Faster is good, as long as that speed increase ALSO allows faster and STABLE throughput advances as well, otherwise one might as well run a pair of 486DX4/100s with a few gigs of memory and superclocked to boot(pipelined, of course). Why CPU speed is so important when the whole system is in dire need of revamping, THAT is what's really needed, not raw CPU clock speeds. The P4 is just starting to grow and "walk" now....but soon, we'll all see apps targeted for the huge bandwidth that has yet to be tapped into, let alone made use of with out-of-date whetstone this; drystone that "speed" tests that prove NADA about the TOTAL SYSTEM THROUGHPUT, not just the dumb CPUs core architecture! Athlon/Duron this, P-whatever that...SO WHAT! Personal choices dictate what we buy and use, no matter what is talked about on /.. I don't see the relevance of AMD over INTEL when the main discussion is over clock speed; it's useless data that many here neither make use of, nor need, just a form of bragging rights to say that, Hey! I've got an Athlon that'll blast those chumpy PIIIs out the hatch, and those PII users claiming the Athlon is crappy oven gear! It all boils down to one thing ONLY....CHOICE! If I "want" a P4, but can only afford a Celeron, so what...same goes for those crying for sledgehammers being able to afford only a K5 CPU.. It's all about choice and now; price. I have been reading numerous threads over clock cycles and it's getting to be very monotonous to say the least. NOBODY cares for processing POWER, the true measure of ALL systems, not just clock cycles......It's how fast you can do many things at once and still maintain a high throughput speed on the CPU, bus, FPU/ALU and video. How many here can run this oft exhalted "quake" game to the max, PLUS access I-net, browse, chat and still keep the whole system running at the rated clock speed/s? NONE, I am more than willing to bet....shame though, 'cuz THAT is where the speed comes into play. "Power is the system, not the CPU"!(not alone, anyhow). If the clock speed of any CPU is so "hot"...take the damn thing out of its "cage" and run the whole system without the support architecture...can't be done, huh? Chipsets, bus architecture/s, memory, cache, H.D. access speed; all of the "system" comes into play heavily, and that is where you MUST begin. Slowest component that needs speeding up, then the next and so on....til you have the fastest PC on the planet. Then of course, it'll be time to buy new again because AMD/INTEL desided to up the anty and "make" you get more, faster, better, slicker...LMAO!

    --
    206.39.38.2, DDN-BLK-36, DOD NET INFO CENTER. 800.365.3642 206.36.0.0-206.39.255.255 NET RANGE.
  65. Re:Half a mil? Isn't that a bit large? by screwtheNSA · · Score: 1

    Okay now, I have a father that owns a machine shop, and i too, have been a machinist as well. The "mil" in "our" jargon/lingo stands for 1/1000th of an inch(.001). This folks, is NOT difficult to comprehend is it? Okay, here goes a small sampling: 10 mils = 10/1,000s inch, or .10 100 mils = 1/10th of an inch, or .10 1,000 mils is...ONE INCH! get it? Got it? GOOD!!! Good day! P.S. By the way, if any of you have a few PIs or PPros or even PIIs and PIIIs lying about and "need" to part with them or just plain toss them away...send them to ME! C.O.D of course.... They have no value, except in my computer room where they will be popped open, pins up and coated in resin and placed under a magnification device so people can see what REAL silicon looks like when the hood's opened. I have 20 so far...need many more though to give a show..Hell, I'll even take AMD too. I show no prejudice in my electrosurgical methods, they all die equally, but do NOT float though. Let's see, what CPUs would be "fun" to fracture....PIs, PIIs, PIIIs...PPros...486DX4/100s....you get the pic I think*S*. Thank you fellow power users for your generous gifts.... Sincerely Crazy Ivan...

    --
    206.39.38.2, DDN-BLK-36, DOD NET INFO CENTER. 800.365.3642 206.36.0.0-206.39.255.255 NET RANGE.