Linked by Thom Holwerda on Sun 3rd Jun 2012 22:04 UTC
Windows So, I've been using the Windows 8 Release Preview since it came out, almost exclusively (except for work, since I'm obviously not going to rely on unfinished and untested software for that). I already knew I could get into Metro on my 11.6" ZenBook, but on my 24" desktop, things aren't looking as rosy. Here's an illustrated guide of the most pressing issues I run into, and five suggestions to address them. Instead of just complaining, let's get constructive.
Thread beginning with comment 520712
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[9]: Comment by gmlongo
by lucas_maximus on Mon 4th Jun 2012 12:23 UTC in reply to "RE[8]: Comment by gmlongo"
lucas_maximus
Member since:
2009-08-18


...says the person who just posted like 5 comments stating that how I use my computer is wrong. Ironic much?


It sounded pretty dumb to me, when whoever designed the UI put in mechanisms that didn't require you to do that so you could get on with other things ... just me

See what happens when you're doing some heavy lifting and you happen to mouseover on the show preview arrows. Saying it doesn't impact performance is laughable, at best.


If it is heavy Network activity ... maybe. But if you are talking about CPU time or disk I/O either you have insufficient ram or I am calling bullshit.

I hit 90% CPU time on a compile on my dev box of 90+ C# projects, the compile time is more than several minutes on a Xeon CPU ... and I can browser the web fine on JS/Image heavy sites at the same time.

Edited 2012-06-04 12:25 UTC

Reply Parent Score: 2

RE[10]: Comment by gmlongo
by bhtooefr on Mon 4th Jun 2012 15:29 in reply to "RE[9]: Comment by gmlongo"
bhtooefr Member since:
2009-02-19

If you're using any browser that isn't Chrome, yes, it does impact CPU time.

When I'm on JavaScript heavy sites on my mini-laptop (1.2 Core 2 Duo, FWIW), I can hear the CPU fan ramping up significantly, and the machine gets more sluggish. CPU fan ramping up means it's not a RAM issue (the HDD indicator would be on, for swapping, which I also see often).

Reply Parent Score: 2

RE[11]: Comment by gmlongo
by lucas_maximus on Mon 4th Jun 2012 16:21 in reply to "RE[10]: Comment by gmlongo"
lucas_maximus Member since:
2009-08-18

If you're using any browser that isn't Chrome, yes, it does impact CPU time.


A 1.2ghz core 2 duo is 7 years old (I have a Dell D430).

Firefox, IE, Chrome and Opera all have the JIT compilation techniques.

Reply Parent Score: 2

RE[11]: Comment by gmlongo
by lucas_maximus on Mon 4th Jun 2012 16:28 in reply to "RE[10]: Comment by gmlongo"
lucas_maximus Member since:
2009-08-18

If you're using any browser that isn't Chrome, yes, it does impact CPU time.


A 1.2ghz core 2 duo is 6-7 years old (I have a Dell D430).

Firefox, IE, Chrome and Opera all have the JIT compilation techniques, that work rather well.

Reply Parent Score: 2