Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Clash of the Titans Over USB 3.0 Specification Process

Posted by timothy on Sun Jun 15, 2008 10:50 PM
from the so-you'd-cut-this-giant-electronic-baby-in-half dept.
Ian Lamont writes "Nvidia and other chip designers are accusing Intel of 'illegally restraining trade' in a dispute over the USB 3.0 specification. The dispute has prompted Nvidia, AMD, Via, and SiS to establish a rival standard for the USB 3.0 host controller. An Intel spokesman denies the company is making the USB specification, or that USB 3.0 'borrows technology heavily' from the PCI Special Interests group. He does, however, say that Intel won't release an unfinished Intel host controller spec until it's ready, as it would lead to incompatible hardware."
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • 1394 For Life (Score:5, Insightful)

    by vertigoCiel (1070374) on Sunday June 15 2008, @10:53PM (#23805955)
    Ever the more reason to never give up Firewire until they pry it from my cold, dead fingers.
    • Re:1394 For Life (Score:4, Insightful)

      by mrbluze (1034940) on Sunday June 15 2008, @10:56PM (#23805967) Journal

      Ever the more reason to never give up Firewire until they pry it from my cold, dead fingers.
      But why does everything with firewire have to cost an extra $30 or so?
      • by Anonymous Coward on Sunday June 15 2008, @10:59PM (#23805991)
        Because it was designed by Apple.
        • Re:1394 For Life (Score:4, Informative)

          by armanox (826486) <asherewindknight@yahoo.com> on Monday June 16 2008, @12:36AM (#23806549) Homepage Journal
          Also, the royalties are not in effect any longer...
            • Re:1394 For Life (Score:5, Informative)

              by saider (177166) on Monday June 16 2008, @08:01AM (#23809231)
              IIRC, Firewire controllers need to be smarter than USB controllers because they might not be hooked up to a PC. For instance, your video camera might go straight to a recording deck, or some other electronic doodad. So the firewire controllers were designed to offload a lot more of the protocol to move stuff around, which made it easier to design systems. Of course this was done back before embedded controllers running Linux (and its USB stack) became cheap as dirt.

              Firewire's main advantage now is the fact that it is a point to point mechanism, not a bus. USB suffers because every so often the host must interrupt things to discover new devices. This can slow down large block transfers quite a bit.
              • Re:1394 For Life (Score:4, Informative)

                by pjrc (134994) <paul@pjrc.com> on Monday June 16 2008, @01:56PM (#23813881) Homepage Journal
                Is is true all downstream devices on a single host controller share bandwidth. But USB control transfers to enumerate devices are such a tiny fraction of the available bandwidth that their impact is virtually zero.

                The thing that does have a big impact is using 12 mbps or 1.5 mbps devices in a way that they hog the bus. Ideally, all non-high-speed transfers would be converted to 480 mbps.

                You might imagine a motherboard with 10 USB ports could communicate with all 10 independently. But that is rarely the case. Usually they all share the same bandwidth. You might expect there would be buffering for 12 and 1.5 mbps transfers, so they wouldn't hog the bus from the other 9 boths. That too is rarely the case.

                USB 2.0 hubs do buffer and convert 12 and 1.5 mbps transfers to 480 mbps. Again, you might expect a 4 port hub to properly allow 4 slow devices to share. That is sometimes the case. Better hubs have multi-TT (transaction translators, basically the USB term for a buffer). But many hubs have only a single TT, which means only one downstream 12 mbps or 1.5 mbps device can talk at once, and any others on that hub must wait until the single buffer is available.

                If the USB 2.0 spec had required all hubs to include a TT on every downstream port, and had the "root hub" (on the motherboard which provides many ports with shared bandwidth) been required to implement TTs on every port, there would have been much higher levels of satisfaction with USB 2.0.

                The when Compaq, HP, Intel, Lucent, Microsoft, NEC and Philips wrote the USB 2.0 spec, they apparently believed 480 mbps speed would soon replace 12 mbps in most devices. Requiring many TTs probably seems excessively costly to support legacy devices that would soon become obsolete. What instead happened is only certain devices requiring high speed implemented 480 mbps. Almost all others stayed at 12 mbps. Most devices that implement 12 mbps use a 48 MHz clock internally, and many low-cost silicon fabs really only supports clocks to about 60-100 MHz (especially if the chip's fab supports the extra polysilicon layers for implementing flash or eeprom).

                Let's hope they learn their lesson and require TTs in ALL cases where 480, 12 and 1.5 mbps devices could share the upstream bandwidth, especially on motherboards. If they do, USB 3.0 will probably be very nice, providing so much more shared bandwidth than necessary that hardly anybody will care if it's shared. But if they skimp and allow any sharing, anywhere, without TTs - the result will probably be a lot like USB 2.0 - very fast, but sometimes you plug in another device and all of a sudden it sucks.
      • FireWire requires an actual IO controller, where USB 2 relies on the CPU and the driver.

        In short -- FireWire is faster and requires far less load on the target machine. The downside is the initial cost is higher. I find it pays for itself pretty quick.
        • by EmbeddedJanitor (597831) on Monday June 16 2008, @03:31AM (#23807445)
          Firewire might pay for itself in high speed applications where time == money, but it is sever overkill (and too high cost) for many lower speed applications such as mouse, keyboard etc. USB is king of the low speed domain because of low cost: a USB-cappable microcontroller only costs a couple of bucks and a sub dollar micro can do a low speed bit-banged implementation of USB. Adding USB to peripherals is almost free.
          • Re:1394 For Life (Score:5, Informative)

            by Jeff DeMaagd (2015) on Sunday June 15 2008, @11:29PM (#23806181) Homepage Journal
            You're wrong. You are basically remembering something that's been fixed and settled a decade ago. Good job on being out of date by a decade.

            The entire royalty is something like $0.25 per device, Apple only gets a portion of that.

            The cost is in the smarts, each device requires a more complicated controller and an additional chip.
              • Just how many Firewire ports have you ever seen on a single device? Would they even add up to more than $5 in royalties?
                • Re: (Score:3, Insightful)

                  by Anonymous Coward
                  You seem to think this article is about sub-Gbs speeds. Sure, Firewire is the king there. But this is the next level and Firewire don't come close on speed.

                  Look on it from the bright side, a few years from now you and your likes will claim how Apple popularized USB3. If it weren't for Apple we would still be using low speed Firewire and so on. Great, isn't it.
                • Re:1394 For Life (Score:4, Interesting)

                  by Mattsson (105422) on Monday June 16 2008, @03:56AM (#23807559) Homepage Journal
                  $1 per port would make quite a difference on a low cost device, especially if it's got two ports or more.
                  Think a 6 port firewire-hub. That's $6 just in royalty.
                  But I don't think they actually charged that much. Wasn't it more along the lines of $0.25 per device?

                  The biggest reason why USB was a really slow hit with the x86-crowd was the lack of USB-support in MS-Windows and other x86 OS's. In order to connect a USB-device you had to install USB-support, reboot, install the device drivers, reboot, sometimes there would be another driver to be loaded after the first one (sic) so another install, reboot...
                  Also, some early USB equipped x86-mainboards didn't have USB support in BIOS, so you couldn't use a USB-keyboard to change BIOS-settings, enter Windows safe-mode, etc, etc.
                  USB was also slow as hell for most other uses than HID-devices or printers.
                  My first mp3-player would take more than an hour to fill. 6GB @ 12Mbps, the horror!

                  When Apple put a port in their hardware, they usually already got the drivers ready and they rely mostly on making their own hardware.
                  The Imac came with a USB-keyboard and USB-mouse made by Apple, and thus everyone that had an Imac used USB-gear.

                  What has MS license cost or Microsoft's greed got to do with firewire royalty and Apple's greed?
                  They're not connected. Don't confuse subjects.
                  If anyone accuses Apple of greed, that doesn't mean that they think Apple is worse than Microsoft. Both are greedy. Microsoft more than Apple usually though.
          • by Anonymous Coward on Monday June 16 2008, @02:33AM (#23807197)

            USB2 is quoted as having 480Mbps throughput, however as the grandparent points out USB2 is not a fully-fledged I/O controller just the PHY layer, the host having to do all the heavy lifting.

            The upshot is that when you actually use one bus or the other to, say copy files, firewire at a mere 400Mbps trounces USB2 in throughput.

            Yes USB3 is in the pipe with vastly improved on paper specs, but then again Firewire has 3200 and 6400 variants in the pipe as well.

            Essentially USB should have been left as an interface for keyboards and mice, and firewire aught to have been adopted by intel as the preferred bus for all high throughput applications, it would also have been preferable to SATA.
          • Re:1394 For Life (Score:5, Informative)

            by CrackedButter (646746) on Monday June 16 2008, @02:35AM (#23807205) Homepage Journal
            How is this modded interesting, all the geeks know that FW 400 is still faster than USB 2.0 because 480mbps is theoretical and not an actual constant transfer speed like with FW400. Firewire is processor independent as well since it has its own controller whereas the main CPU is used to control USB 2, that means its transfer rate is dependent on system performance. Everything else in your post isn't bollocks though.
          • Re:1394 For Life (Score:5, Informative)

            by DDLKermit007 (911046) on Monday June 16 2008, @05:24AM (#23807949)
            Great way to stay on the sidelines of understanding. Yes, USB 2.0 is "faster" than Firewire on paper. However, 2.0's max/burst speed of 480Mbit/s is very different from it's average speed (about 240Mbit/s), and substantially lower than Firewire's sustained speed. It's a side effect of something that relies on the host to do the heavy lifting vs a device that handles it's own heavy lifting. Not looking forward to similar crap with USB 3.0, not to mention the continuance of shitastic driver support I've always seen from USB vs Firewire.
          • Re:1394 For Life (Score:4, Insightful)

            by enoz (1181117) on Monday June 16 2008, @12:29AM (#23806513)
            If someone has physical access to your computer then it is already game over*.

            Why bother using firewire hacking when it is much simpler to do a hard reset and load a bootable CD?

            *YMMV, See TrueCrypt for example.
    • Viva IEEE 1284 FTW
      • Re:1394 For Life (Score:5, Interesting)

        by Jeff DeMaagd (2015) on Sunday June 15 2008, @11:25PM (#23806153) Homepage Journal
        I've not heard of USB missile launchers either. It shoots USBs?

        True, there is no HID standard for Firewire. But that's not its strength. Firewire's strength is USB's weakness, and Firewire's weakness is USB's strength.

        Firewire seems to be fading into smaller niches though. I don't want to daisy chain hard drives, so eSATA will do fine, and eSATA does allow the use of port multipliers, one port still does five drives.

        I have two HDV cameras, but I don't use them much, I prefer an HF10 which writes to SDHC cards. Firewire is good for audio tasks, which I don't do.
        • Re:1394 For Life (Score:5, Informative)

          by Tubal-Cain (1289912) on Sunday June 15 2008, @11:34PM (#23806207) Journal

          I've not heard of USB missile launchers either. It shoots USBs?
          http://www.thinkgeek.com/geektoys/warfare/8a0f/ [thinkgeek.com]
        • Re:1394 For Life (Score:5, Interesting)

          by evilviper (135110) on Monday June 16 2008, @01:10AM (#23806725) Journal

          Firewire seems to be fading into smaller niches though. I don't want to daisy chain hard drives, so eSATA will do fine, and eSATA does allow the use of port multipliers, one port still does five drives.

          It's not USB2 or SATA that cannibalized Firewire's supposed market... It's Ethernet.

          Much better range, lower price, more devices, equally high speed, similar (controller) requirements, easier device sharing, etc.

          High-end printers, scanners, CD/DVD duplicators, studio (audio/video) equipment, hard drive arrays, etc. They all have gigabit ethernet connectors now.

          Ethernet ate the high-end, USB ate the low-end, Firewire got left out in the cold, with just a few niche applications where Ethernet is inconvenient and its benefits don't apply, and yet USB isn't quite fast/flexible enough. That basically means just digital camcorders, and a handful of studio equipment...
      • Re: (Score:3, Interesting)

        Thing is...your examples are easily served by USB 1, without even taking us into area of USB 2. Which is usefull basically only when dealing with large storage and video devices, and those areas are very well covered by eSATA and Firewire.

        So...with USB 3 we have a case of extending USB into areas which it wasn't really meant to serve...and which already are served very well.
        • Not to mention that USB1 is really just a user friendly replacement for the old reliable RS232, and PS/2.
          • Re: (Score:3, Insightful)

            Not to mention that USB1 is really just a user friendly replacement for the old reliable RS232, and PS/2.
            ..and IEEE 1284 (Parallel ports), and SCSI-1 (see: Pre-USB scanners, CD Burners, HDDs), and PCMCIA (see WiFi, Flash, Floppies, Zip drives, etc.), and...
            • Re: (Score:3, Insightful)

              ...and game ports, and TOSLINK, and MIDI ports, and PCI slots (to a significant extent), and ADB, and infrared ports, and...
      • Re:1394 For Life (Score:5, Insightful)

        by v1 (525388) on Monday June 16 2008, @12:13AM (#23806413) Homepage Journal
        Firewire is not designed to run peripherals. It's designed for high speed, efficient transfer of data. The closest it gets to peripherals is high end scanners. Mice, printers, keyboards, basically anything human interface is more appropriate for USB. Universal Serial Bus. Firewire is not universal. The overhead created by being universal makes even the high speed USB (480) transfer data slower than Firewire 400. Then there's Firewire 800 which leaves USB in the dust nicely on file transfers.

        Also firewire IO is done on the card/chip, whereas USB is done to a large degree by the CPU. This is why we saw recent threads about the 'security risk' associated with jacking into the firewire port of a computer - you have direct access to system memory on most systems. Try a file copy with USB 2, and again with firewire, watch your processor. BIG difference. This is important when you are processing video, you can't have your video IO making your video processing lag and skip frames. That's one of the reasons firewire remains dominant on video.

        The only aspect of this I find puzzling is the scarcity and cost of firewire flash drives. kanguru makes them but they cost 3-4x as much as comparable USB thumb drives. Best guess here is thumb drives started their boon before most PCs had firewire ports, so they were just trying to hit the largest market, which lacked firewire, and so now we're stuck with it.
  • So... (Score:5, Interesting)

    by Darkness404 (1287218) on Sunday June 15 2008, @10:54PM (#23805963)
    So will this mean in the end we will have 2 competing USB standards? USB-Intel and USB-AMD? I can only hope that one will get picked over the other before it appears in most products because after the whole HD-DVD and Blu-Ray thing it would be an absolute pain to get a computer with USB-Intel in it when all the products will be USB-AMD.
    • At least with a computer you could just install a $20 PCI card, little bit harder with a DVD player.
    • Once again, we'll have the VHS version and the Betamax version.

      One will win. Avoid whichever one Sony gets behind.

      • by sznupi (719324) on Sunday June 15 2008, @11:31PM (#23806189) Homepage
        Sooo...you're still waiting for HD-DVD to win?
        • by symbolset (646467) on Monday June 16 2008, @12:25AM (#23806501) Journal

          Sooo...you're still waiting for HD-DVD to win?

          This one's not over yet. Apparently online distribution was a third contender waiting in the wings. We shall see. Sony bought out HD-DVD. They can't buy out online distribution. In the meantime BD players and discs have gone up in price not down. That was a critical mistake.

          Sony has some of the most brilliant engineers on earth. They're chained to the marketing team from hell. They always try to exploit their market share before it's time. A shame, really. They do a host other things wrong too. If it weren't so their supercomputer class gaming console [wired.com] would not be coming in third to the XBox and the Wii. They could use a consultant to come in and tell them how retarded their marketing team is, but they have too much pride to win. Surely I'm not the only one who sees this.

    • by Phong (38038) on Sunday June 15 2008, @11:47PM (#23806279)
      This isn't about competing USB 3 standards -- the spec is being designed by a group, and there is only one. This is about the design of the hardware used to implement a host controller that can comply with the spec. This is something that any company can develop if they want to, but since Intel is going to license their design of the host controller for free, most companies will just wait for that design and use it to implement USB 3.
    • Re:So... (Score:4, Informative)

      by Hal_Porter (817932) on Monday June 16 2008, @01:01AM (#23806671)

      So will this mean in the end we will have 2 competing USB standards? USB-Intel and USB-AMD?
      I think this is about host controller specs not wire protocols. So it will be like with USB 1.0 where there was OHCI and UHCI. Universal Host Controller Interface was Intel and Vias controller standard and OHCI was everyone else's. Including Microsoft. OHCI was supposed to be do more in hardware, though I don't think it made much difference in practice. But both controllers were compatible on the wire - you could easily make devices that worked with both. IIRC there were cases where the OHCI controller, because it had more informatation about the protocol could respond to information from a device inside the same frame. UHCI controllers were basically dumb and needed intervention from software on the host, so they'd respond to some device condition during the next frame, after the host stack had had a chance to think.

      But according to the USB spec both behaviours are correct since the device can't make any assumptions about what overheads exist on the host.

      I can't find the reference to device visible differences between UHCI and OHIC and in any case it was a very rare case. I did find this presentation by Intel that shows OHCI and UHCI performing almost identically despite the fact that OHCI controllers basically do the USB protocol in software and UHCI is just a bus master DMA engine attached to a serial interface with the protocol is done in software.

      http://www.usb.org/developers/presentations/pres0598/bulkperf.ppt [usb.org]

      With USB 2.0 there was a push to a unified host controller spec called EHCI. From what I can tell this spat means that there will possibly be two rival host controller specs because Intel haven't published their spec in time for other people to implement it. But I don't think that will fork the wire protocol, I think it just means that OSs will need to have two new host controller like USB 1.0 drivers rather than one like USB 2.0.

      You could argue that UHCI was a good thing since it uses less hardware and performs about the same.

      Incidentally Wikipedia writes this up based on the "Good open standards vs vile proprietary standards" meme, which seems a bit unfair. Both OHCI and UHCI are based on published specifications which are freely available. I don't know if you need to pay a license fee to implement either or both of them - I actually think you don't since USB was successful because you didn't need to pay a per port fee when it was introduced, unlike Firewire.

      http://en.wikipedia.org/wiki/OHCI [wikipedia.org]

      The difference seems to me more like a software engineer view (Microsoft want to do it all in hardware like OHCI) of the world vs a hardware engineer view of the world (Intel say do it all in software with UHCI)

      • Re:So... (Score:5, Insightful)

        by Gnavpot (708731) on Monday June 16 2008, @12:23AM (#23806489)

        All other things being equal (no major bugs in one of the specs), USB-Intel would be the clear winner if the two standards came out about the same time, due to Intel's influence, name recognition, prestige, etc. The 5000 pound gorilla flattens the 200 pound monkey with 1 step.

        Oh, you mean like Intel won over AMD with their attempt at a 64 bit processor instruction set?

        (In case you don't know: They did absolutely not. Intel had to scrap their 64 bit processor because nobody wanted it, and today's Intel 64 bit processors uses AMD's instruction set.)
  • Bastard companies (Score:4, Insightful)

    by mark_hill97 (897586) <masterofshadows@noSPaM.gmail.com> on Sunday June 15 2008, @11:07PM (#23806039)
    As we have seen with wireless networking gear in the past companies are all too eager to screw the consumer with incompatibilities because of pre-spec products being released. If Intel was doing this I would say good for them, its rare a company would actively try to protect the consumer from these vultures.
  • by spinkham (56603) on Sunday June 15 2008, @11:11PM (#23806061)
    This is a replay of the OHCI/UHCI host controller interface standards of original USB.
    This does NOT at all effect users, only driver writers.
    What is being forked is the USB driver interface, and does not effect device compatibility at all.
    As mentioned above, there were two driver interfaces for the original USB standard, and the only people who knew were driver writers and nerds compiling their own custom kernel.
    This is blown way out of proportion, and doesn't effect 99.999% of us. Nothing to see here, move along....
    • Re: (Score:3, Informative)

      ... and people who ran into all sorts of nasty incompatibilities in the more scary corner-areas of the spec (isochronous transfers, etc.). Microsoft remember this fun which is why they are not happy about this. I remember various issues with USB depending on whether you had and OHCI or UHCI controller.

      It is not in the interests of the consumer nor of the standard to have multiple host-controller interfaces. You may care to muse on why it might be in Intel's interests to the detriment of all others.
  • by nick_davison (217681) on Monday June 16 2008, @01:41AM (#23806877)
    Intel has a point: releasing documentation on a non finalized standard creates a fluster-cluck of bad implementations that aren't necessarily compatible with each other. IIRC, isn't that what's happened to 802.11n, pre-n, draft-n, n-ready, looks a bit like n in a dress, MIMO, etc. which just confuse the crap out of a consumer already pissed at USB 2.0 HiSpeed and USB 2.0 FullSpeed crap.

    nVidia has a point: Intel not telling anyone else until the last moment would, indeed, give Intel an unfair first mover advantage.

    Obvious solution: Release the pre and post release specs with an agreement attached that anyone wanting a copy has to sign. An amount of time that gives everyone a fair chance to get product ready is picked after final specs are chosen. Anyone gaining access to the specs agrees not to release until that time period has passed. Now no one releases incompatible hardware and no one gets an unfair first mover advantage.
  • by ILuvRamen (1026668) on Monday June 16 2008, @01:54AM (#23806957)
    If any one of them was really smart and wanted to name it to win, they'd name it either blu-port, usblu, or usb 4.0. I mean seriously, which one are you going to use? One named USB 3.0 or 4.0?
      • by zappepcs (820751) on Sunday June 15 2008, @11:44PM (#23806257) Journal
        I agree... the battle just heating up, how can you be biased? Not until there are two definitive sides can you get behind one or the other.

        This does point out one thing, there is a lot to be said for open standards ... even if some of them have been OOXML'd lately. (that's not even valid in Roman Numerals)

        No matter which version is better technically, if there is one that is not backwards compatible they will have an uphill slog trying to sell it. Yeah, I know, CDs were not backwards compatible with floppy drives, but this is a bit different. If the connector is the same, it MUST be compatible or my aunt nelly will kill someone.

        • The two sides I see here are not Specification A and Specification B but not producing an open standard and producing an open standard.

          "there is a lot to be said for open standards"... Yes, Something indeed. Who lead the CD revolution? Sony. Who developed the standard? Sony (and Phillips). They released the standard after they had working products to sell. The "standard" still then cost a lot of money to even look at. (See the wikipedia article on the Red Book standard).

          My Point (finally?): Giving the ex
          • by zappepcs (820751) on Monday June 16 2008, @01:19AM (#23806769) Journal
            Interestingly (or not) you demonstrate a logical understanding of the technology marketplace. To paraphrase you, if I may, Intel and AMD are fighting about who gets to piss on the idea of competition creates value for the consumer. Any space where AMD and Intel are competing is full of this, and not inconsequentially, lawsuits. Intel has been partnered with MS for a long time, and they worked hard to be the hardware version of what MS was to software.

            We can detail the lawsuits ad nausea, but my point is that anyone that was a healthy partner with MS has done to their industry what MS did to software. Like that or not, it is true. In the end, we have Mr Gates to thank for this, no matter how philanthropic he may try to be these days. I wonder sometimes how far exactly he has set the human race back from what will eventually, and necessarily be.

            Though that is sort of scifi philosophy, it is true. In the name of riches, the advancement of technology has been slowed, deliberately, and with malicious intent against the betterment of mankind. In this way, I find his generosity a bit pale these days.

            Open standards are indeed the ONLY way to create technology and advancement that will last and actually advance mankind in a direction that betters all of us. Despite the socialist sounding tone of that, it is true. We are all better for the sharing of technology from the space race. Technology, and specifically computing/networks are still in the hands of those that would derail it's benefits if there is profit in it. There are those that are trying to change this situation, but it is slow going. Even hardware manufacturers are hobbled by things like the DMCA and it's ilk around the world. Sometimes I'm sad to say I'm American.

            Fighting against the 'right thing to do' for the sake of money is not in the best interests of the community, and in the end, it hurts your business. Customer is king, so they say, and when you put hurdles in the way of a complete and exemplary experience by the end user, you harm your business in some way, if not in big ways. It's unfortunate that not enough people will understand that the competitions in the technology markets have hurt them, and they will not understand how to express their frustration that older USB devices won't work with new USB hosts. It will be just one more black magic thing they don't understand about technology type things. They will go to PCs R Us and buy whatever the best they can get happens to be, hoping that it works for a couple of years, not unlike car buyers. So for profits, businesses promote the throw-away society. When there is something new, throw the old away, don't upgrade, don't re-use. How is this helpful to the human race?

            Well, just some late night thoughts about this whole thing, and the absolutely ignorant waste it makes of the world.

            BTW, there is hardware space competition.... if you are willing to build your own and not buy what the idiot^H^H^H^H^H salesman tells you at worstbuy.

            sigh