Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome will use gpu to render pages

blog.chromium.org

Post reply on HN
Print view View original

41–49 of 49 posts

Re: Chrome will use gpu to render pages

#41

Post by jamesbritt »

andreyf wrote: post #27
jamesbritt wrote: post #23

Earlier quoted context omitted.

"IE releases are still tied to the years long windows ship cycle, ..." I'm pretty sure I get notifications for Windows Updates when there's a new version of IE. And even if not, I've somehow gotten IE 7 or 8 on an XP install, so it's no different than when Mozilla or Google announce a new release. If you want it, you get it.

If you want it, you get it. The people who want it are irrelevant. So are the people who don't want it. Both are minorities compared to the people who don't care, and just pick the default option. Chrome's default is to silently upgrade, and light a tiny orange dot when you need to restart.

"Chrome's default is to silently upgrade, and light a tiny orange dot when you need to restart."

I ended up with IE8 because I ran Windows Update, not because I had some desire to get a new IE.

My guess is that most Windows users are going to let the updater run, and get new versions of IE.

Re: Chrome will use gpu to render pages

#42

Post by patrickaljord »

protomyth wrote: post #40
patrickaljord wrote: post #38

Earlier quoted context omitted.

> 1 250mb internet download vs. 4-8mb Make that a few kb. And last time I checked at my work, admin updates usually happen during work hours and affects people working in the "lab". Also, it's 1 250mb that is sometimes installed on each machine on the network, so way worse than a few kb.

Well, your admin is doing it wrong if updates are happening during the day. So, no people bothered, reports, and less internet usage is better.

Your admin is doing it wrong if updates of a few kb are clogging his network. Also, small labs can't afford to pay admins at night, and big labs surely can afford a few kb transfers on their networks. We're talking about gigabytes networks and admin can always use cache proxy so that chrome only taps the net once for the tiny kb update.

Re: Chrome will use gpu to render pages

#43

Post by melling »

fjarlq wrote: post #26
melling wrote: post #18

Earlier quoted context omitted.

IE still has 60% market share, and it's holding steady. IE9 is going to be one of the most important products Microsoft ever ships. It will be compatible enough with web standards, and offer enough performance, that it should allow developers to build more sophisticated apps based on open standards. Html5, css3 and fast Javascript will soon be a given.

Holding steady? How do you figure that, exactly? http://en.wikipedia.org/wiki/Usage_share_of_web_browsers#His...

I figured that because between June and July, IE marketcshare increased by .4%

http://marketshare.hitslink.com/browser-market-share.aspx?qp...

Re: Chrome will use gpu to render pages

#44

Post by InclinedPlane »

protomyth wrote: post #37
patrickaljord wrote: post #35

Earlier quoted context omitted.

> We all don't have the same internet connections that Mountain View has. Luckily, Chrome use differential updates. This means each update is a tiny binary patch. If you combine them all on your network, it's still a smaller update then one single IE update of 250MB deployed to each machines.

1 250mb internet download vs. 4-8mb for a couple hundred machines on the internet line is a big difference. Particularly since I can plan when the big download happens (and update) versus all the small downloads that happen in a lab at the same time because of a class starting. Students with the first class of the day don't feel terribly happy about being the designated updater of some company's software.

I highly suspect that you are projecting the experience of other auto-updating software (such as Adobe Reader) onto Chrome. Chrome's auto-updates are incredibly efficient and very non-intrusive.

Re: Chrome will use gpu to render pages

#45

Post by tuxychandru »

protomyth wrote: post #34
tuxychandru wrote: post #33

Earlier quoted context omitted.

The automatic and frequent update system is one thing which makes Chrome very good. It can pretty much be assumed that all users connected to the internet would be atleast on the latest stable version.

Actually, in a place with a good internal network and a lower speed external connection, it makes Chrome very bad. Taking up bandwidth downloading the same thing for multiple computers is bad. Windows and OS X allow one download to be propagated to multiple machines. This is an efficient model that allows reporting on which machines didn't get the update (thus making it a lot more likely all machines will be updated)…

The problem with allowing admins to manage updates is that any new version which breaks an internal app in the slightest way would be a reason to avoid updating.

This is what has given IE6 its long life in the corporate world. While this is a pragmatic decision, it can hurt badly in the long run as we all know.

Re: Chrome will use gpu to render pages

#47

Post by protomyth »

tuxychandru wrote: post #45
protomyth wrote: post #34

Earlier quoted context omitted.

Actually, in a place with a good internal network and a lower speed external connection, it makes Chrome very bad. Taking up bandwidth downloading the same thing for multiple computers is bad. Windows and OS X allow one download to be propagated to multiple machines. This is an efficient model that allows reporting on which machines didn't get the update (thus making it a lot more likely all machines will be updated)…

The problem with allowing admins to manage updates is that any new version which breaks an internal app in the slightest way would be a reason to avoid updating. This is what has given IE6 its long life in the corporate world. While this is a pragmatic decision, it can hurt badly in the long run as we all know.

So, it's preferable to have a company not able to use its apps to get business done then have a non-updated browser?

Re: Chrome will use gpu to render pages

#48

Post by andreyf »

jamesbritt wrote: post #41
andreyf wrote: post #27

Earlier quoted context omitted.

If you want it, you get it. The people who want it are irrelevant. So are the people who don't want it. Both are minorities compared to the people who don't care, and just pick the default option. Chrome's default is to silently upgrade, and light a tiny orange dot when you need to restart.

"Chrome's default is to silently upgrade, and light a tiny orange dot when you need to restart." I ended up with IE8 because I ran Windows Update, not because I had some desire to get a new IE. My guess is that most Windows users are going to let the updater run, and get new versions of IE.

I ended up with IE8 because I ran Windows Update, not because I had some desire to get a new IE.

Exactly. Chrome updates faster because it does it with zero user input. It just happens whenever spare resources are available and politely lets you know when it's done. IE8 needs you to run Windows Update, which a significant number of users don't want the hassle.

Re: Chrome will use gpu to render pages

#49

Post by jamesbritt »

andreyf wrote: post #48
jamesbritt wrote: post #41

Earlier quoted context omitted.

"Chrome's default is to silently upgrade, and light a tiny orange dot when you need to restart." I ended up with IE8 because I ran Windows Update, not because I had some desire to get a new IE. My guess is that most Windows users are going to let the updater run, and get new versions of IE.

I ended up with IE8 because I ran Windows Update, not because I had some desire to get a new IE. Exactly. Chrome updates faster because it does it with zero user input. It just happens whenever spare resources are available and politely lets you know when it's done. IE8 needs you to run Windows Update, which a significant number of users don't want the hassle.

" IE8 needs you to run Windows Update, which a significant number of users don't want the hassle."

I think we're each arguing from incompatible anecdotes.

Post reply on HN