Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:He's wrong. (Score 4, Insightful) 649

by the linux geek (#39314697) Attached to: <em>Battleheart</em> Developer Drops Android As 'Unsustainable'
Version diversity isn't the only kind. Implementation and hardware diversity matters too - for instance, I've run into a crash bug when attempting to start a new Activity from within a TabHost that only occurs on Galaxy S devices. That sort of thing is really incredibly frustrating, and makes QA far more of a pain in the ass than it should be.

Comment: Re:botched processor design? (Score 1) 497

by the linux geek (#39088363) Attached to: AMD: What Went Wrong?
For specific workloads, Itanium is great. It can sustain 2 FP loads, 2 FP stores, and 2 FMA's in a cycle, which means for certain types of DSP-ish workloads, it has more performance per-cycle than just about any other mainstream CPU. It also has a very high-performance cache hierarchy, with massive blobs of SRAM and a low-latency L1 (one cycle to access.) The problem is that it's expensive, clocked low, and not really ideal for where it's marketed (the mission-critical enterprise server business.) It still has significant advantages over Xeon for some workloads, namely things that are highly cache-sensitive or that scale high enough where directory-based coherence is good to have.

Never worry about theory as long as the machinery does what it's supposed to do. -- R. A. Heinlein

Working...