reply to post by toreishi
i think using the kalashnikov in the comparison is unfair to the kalashnikov; for while the gun is a masterpiece, the planes are
not.
I was merely making a metaphoric comparison of one level of technological refinement to another.
In practical application, it is sometimes better to use a more proven technology, than a newer, potentially better one.
Costs less, more design specialization, existing modification industry and technology...
And in military hardware, performance under duress is more important than better white sheet specs.
and the quaint plane that Edrick is proposing (w/o or with lesser computers, etc) would be like an ordinary telescopic sight, while the F-22
would be more akin to the hubble space telescope.
Why would you want to attach the Hubble space telescope to a Rifle?
in the F-22, those same computers analyzes the returns as it acquires and confirms the target.
Well, let me put it to you this way...
The Raptor’s software is composed of over 1.7 million lines of code...
Windows NT 3.1, 4-5 million lines of code
Windows NT 3.5, 7-8 million lines of code
Windows NT 4.0, 11-12 million lines of code
Windows 2000, 29+ million lines of code
Windows XP, 40 million lines of code
Windows Server 2003, 50 million lines of code
Odds are, that the OS the Raptor uses is not going to be able to do the following:
View JPG's
View MPG's
Playback MP3's
View HTML
etc, etc, etc...
When the CIP in the raptor begins analyzing the signal to noize ratio of radar returns...
It is not running a GUI, a Device driver registry, multitasking...
It is not running a child process, on an application level program, running on a Machine level Kernel (Translation program)
Every single line that is executed is machine code, fed directly into the CIP, with definitive results.
There is absolutely no need to push multi Gigaflops through your buses...
Most of the "Standard" application level, and child process level code is completely bypassed, and unnecessary.
You would be amazed at how fast computers can ACTUALLY run, when they don't have to translate every instruction from C to Machine code, search
through memory to find dynamically linked objects, handle multiple device drivers from a list of device drivers... etc...
Most of what eats up a computer's processing power is this "Compatibility" level of code, and object handling.
Remove that "Compatibility" layer, and your average 400Mhz will do things that will surprise you.
GUI's are resource hogs, as are Direct X, and File type registries.
-Edrick
[edit on 11-11-2009 by Edrick]