Could be homosexual or asexual too

And the autonomous systems, while good enough for a high-altitude recon/ground attack vehicle such as the x47, are not good enough for a complex environment like air-to-air combat. One of the problems is computational abilities, another is even greater susceptibility to EW than human-piloted aircrafts.

Also, the programmed parameters can't hope to match everything that can happen during a mission.

It's not just a case of having a list of evasive maneuvers. You need fairly complex analysis to evaluate the threats in the environment, and selecting the evasive manuever that best fits, and then adapting that as the action continues.

For where you have a technological lead/EW superiority, that is true. However, assuming combat between fairly technologically equal parties, a lot will come down to pilots individual abilities.

Why manned fighters still have a place: Greater situational awareness, no radio link latency, not as sensitive to jamming.

Doesn't matter how many G's your drone can pull if you have 500ms latency, and your sensors are jammed. And if the radio frequencies are jammed, the drone is a sitting duck, following simple pre-defined actions, while a pilot can figure out a solution/act independently.

He's just bullshitting. He's been spamming the same drivel since at least the Sandy Bridge release, taking no heed to the fact that PCI-E speeds have increased also.

Hell, a PCI-E 4x slot of the 3.0 spec could handle 4 drives of the type in the Mac Pro he's mentioning, since 3.0 increased transfer capacity per lane to 985MB/s when run at 8GT/s.

A 16x slot PCI-E 3.0 slot handles stuff like Infiniband 12x(QDR) easily, which is 120Gbit/s...

And this is a well-known problem, ever since the SGI O2 with its UMA had the same problem. It had top-of-the-line memory bandwidth for a small desktop workstation at the time at 2.1GiB/s for the system RAM, but in terms of 3D performance etc, it was outperformed by what on paper was inferior predecessors unless the dataset was really large(And then the CPU couldn't keep up instead.....)

We already see some of the issues with the new Xbox, while the PS4 won't run into the issues quite as badly, due to going with GDDR5

Anecdote time:

I used to have a dual core Athlon 64, and had a GF 9800GT, and Crysis had to be run at a really low res, with all graphics at bottom settings, and I always attributed that to the GPU.... Then I upgraded to a i5-2500.... And suddenly I could play Crysis at 1920x1080 and even pull up some of the settings to medium or even high... Because the CPU could suddenly keep the GPU fed...

That's not to say that it's rare either. Fibre accounts for roughly a third of all subscriptions for wired internet access here in Sweden. xDSL is a bit over 40%, and cable taking up the slack.

Decompression is, in general terms, computationally insignificant. However, the hardware acceleration support in DX was not for decompression, it was for 3D spatialization and effects. And those are NOT computationally insignificant for interactive scenes, especially not when you have a significant number of audio sources.

It was claimed that uncompressing the audio would tie up an entire core. The large amount is also because they stupidly install all languages at once, even if you select a specific language at installation time.

Industry also has another thing that leads to increased safety: Avoidance of solvent stills for example. Another factor is that in industry, you often work in scale, which leads to avoiding highly exothermic reactions that work fine in academic lab scale, but goes BOOM when you scale it up above 10cl or so...

"a) students are quite gungho when it comes to their work and will quickly take shortcuts because they don't know any better or don't have the right tools, example: I didn't see a wire stripper till I got to industry, I used to do it by pressing the wire to a knife using my thumb and I got many cuts as a result."

Students being the only gung-ho ones? Bwahahahahaha.... Students being gung-ho is a result of PI's and others not having a proper safety mindset, or even deliberately pushing students to ignore safety, or not teaching it at all...

http://pipeline.corante.com/ar...

RTLinux as a solution is not (hard) realtime as they falsely claim it to be. Only the Hypervisor is realtime, but the Linux kernel running as a process is not, since it can't guarantee that it will respond in a deterministic manner. That's the problem with the PREEMPT_RT patch too.

With the Linux kernel, you get an average timeframe for an interrupt. With QNX or other proper realtime OS's, you get a Max timeframe.

Yeah, Cogent really is trying every dirty trick they can to go past any contract limits etc and freeload, and then they cry loudly to the media when they get told to stick to the contract.