D
David Maynard
Mxsmanic said:David Maynard writes:
Mainly because disk and network delays prevent it.
That sentence doesn't make any sense no matter what one thinks it might mean.
The vast majority of computer users are not encoding video.
You must be a real busy beaver taking all these polls of the "the vast
majority."
Not to mention that, even if it were true, encoding video, regardless of
how few or many do it, is still proof that your claim of processor power
being 'all consumed by the GUI' is simply not true.
The market is limited largely to adolescent boys; most other computer
users (including the vast majority of women) don't play video games with
any significant frequency.
More polls again?
Still shows the processor power is not all consumed by the GUI.
The fact that things like DirectX are needed to even get games to run
demonstrates how completely they exhaust available horsepower, no matter
how high that horsepower is.
Utterly nonsensical. Needing graphics support for graphics isn't 'proof' of
anything.
However, machines that are woefully
inadequate for gaming are often generously dimensioned for just about
any other type of application short of weather prediction or nuclear
simulations.
A low power computer might well be fine for light web/office applications
but that says nothing at all about the GUI consuming all the processor
power of more powerful machines. It simply means one doesn't need a lot of
power for low power applications. And I tend to agree.
Most people can resolve considerably less than 100 ms.
Actually, most people can't resolve a single event to that degree. They can
'detect' it's occurrence (visual motion detector like 'whiz by', "what was
that?") but not resolve the timing.
On average, humans have a reaction time of 0.25 seconds to a visual
stimulus, 0.17 for an audio stimulus, and 0.15 seconds for a touch stimulus.
Others generally don't care.
Simply not true, as the giga mega hunka boat load of theme and GUI
enhancement download sites attest.
Tell Stardock that no one cares.
These programs are not just doing I/O to load; they are doing I/O
constantly.
I have no idea what 'these programs' are but common applications are not
doing "I/O constantly," except for the ones you claim "the vast majority"
don't do, like video editing.
It's not shared by geeks, but it is shared by end users, and they are a
much larger part of the user community.
No offense but I seriously doubt you have all that good a handle on what
the 'user community' thinks about bells, whistles, games, HTPC, PVRs, video
and the rest. For one, there's just too many of them with varying needs to
talk about 'the user community' as if it were some monolothic, single
minded, block that 'thinks like you do'.
The processor is usually the strongest link in the chain, even though it
spends most of its time waiting for memory modules to respond.
Now it's memory. Sooner or later you're going to rail against very
component, aren't you?
But this becomes a problem if we don't have to wait for network and disk
I/O. Then we end up waiting for the bells and whistles.
I don't. Why do you?
That's not an appropriate analogy,
It's certainly as inappropriate as yours are.
but you can accurately say that cars
are effectively no faster than 50 years ago because it still takes the
same amount of time to get to work in them.
No, but it's a good example of another appropriately inappropriate measure
because even if getting to work is 'no faster' it has nothing to do with
the *car*.
And the REASON these things matter is if one has even the slightest
inclination to improve any of these supposed 'problems' you're not going to
get anywhere trying to 'fix' the wrong bloody thing.
Much of what modern, well-written applications require is within the
capabilities of a 286. The 286 is indeed slower but an application
written for maximum efficiency on a 286 might well match a bloated
application on a modern system in terms of response time.
As long as you strip out features that, contrary to your exhaustive
polling, many users want and restrict it to simple mundane tasks, such as
your 'text editing' (without auto correction, images, fancy formatting,
version tracking, contextual help, hot fax, email, and the rest), and
remove firewall protection, and graphics support, and anti virus
protection, and automatic system repair, and change history tracking, and
file journalling, and file system security, multi-user support, internet,
auto update, and on and on, then yes. But then you don't have a modern PC
with modern apps if you do.
You're simply barking up the wrong tree with 286 comparisons because I used
to *have* an 8Mhz 286 at work, my notebook was a 12MHz 286, so I used it
instead of the office machine most of the time, and a 16 MHz 286 at home;
and I still have the apps. So don't tell ME a modern computer isn't any
'faster', more useful, more convenient, easier to use, or any other nonsense.
From five MHz to 3200 MHz, plus optimizations that increase the number
of instructions that can be executed on average per clock cycle.
'The processor' is not 'the computer'.
Anything that requires computing power.
Same silliness.
I'd expect argument without personal attacks from the computer literate.
But some of them are angry young males.
Then don't suggest that processor speed is the sole determinate of system
speed when you know darn good and well it isn't.