http://www.anandtech.com/mobile/showdoc.aspx?i=3636
Certainly a different take on benchmarking browsers (which has all got very pointless of late given the marginal differences).
http://www.anandtech.com/mobile/showdoc.aspx?i=3636
Certainly a different take on benchmarking browsers (which has all got very pointless of late given the marginal differences).
turn off flash ftw.
seriously its a pain in the arse, do you want to sacrifice so much of your CPU time, bandwidth and even the you time spent waiting on a netbook
(and yes, we all know safari is a pile of ****)
throw new ArgumentException (String, String, Exception)
If bloat = more cpu cycles yes - does it always? FF isn't exactly light on it's feet now - and remember the focus is on getting 8ms faster rendering of your javascript.
Apple just can't write windows apps period - and in the case of safari it's probably some horrible emulation layer kludge that's making it so awful (seriously, a windows application that looks like a mac app? doh!)
Also don't forget that battery life is effected by the very instructions too. Some consume more powers than others.
I wouldn't want to describe it simply as bloat, as bloat people tend to think of as a memory type issue.
I suspect these are down to inefficencies in proccessing, rather than just memory issues.
throw new ArgumentException (String, String, Exception)
There are currently 1 users browsing this thread. (0 members and 1 guests)