The Chrome Distortion: how Chrome negatively alters our expectations

Post by swiley » Sat, Mar 26, 2016, 3:59 PM UTC

okket wrote: post #54

bdickason wrote: post #48

I think this article is missing the idea of the browser hype cycle (Every 4-5 years): 1. A cool new browser comes along promising a minimal featureset with a focus on speed. 2. Early adopters make the move and start asking for a few features they liked on their old browser (extensions, some customization, etc). 3. The new browser is excited by the growth opportunity and invests in said features. 4. Eventually, the ne…

Such a "hype cycle" can only exist where the OS supports integration of 3rd party browsers (desktop only). On mobile devices you can rarely switch browsers without losing access to major parts of the OS (read: 3rd party browsers can render/view web pages, but forget about integration).

Post by idle_zealot » Sat, Mar 26, 2016, 4:00 PM UTC

okket wrote: post #54

bdickason wrote: post #48

I think this article is missing the idea of the browser hype cycle (Every 4-5 years): 1. A cool new browser comes along promising a minimal featureset with a focus on speed. 2. Early adopters make the move and start asking for a few features they liked on their old browser (extensions, some customization, etc). 3. The new browser is excited by the growth opportunity and invests in said features. 4. Eventually, the ne…

Such a "hype cycle" can only exist where the OS supports integration of 3rd party browsers (desktop only). On mobile devices you can rarely switch browsers without losing access to major parts of the OS (read: 3rd party browsers can render/view web pages, but forget about integration).

Post by johansch » Sat, Mar 26, 2016, 4:05 PM UTC

swiley wrote: post #61

okket wrote: post #54

Earlier quoted context omitted.

Such a "hype cycle" can only exist where the OS supports integration of 3rd party browsers (desktop only). On mobile devices you can rarely switch browsers without losing access to major parts of the OS (read: 3rd party browsers can render/view web pages, but forget about integration).

Opera works great on android (although I guess it's still largely WebKit based)

Post by r00fus » Sat, Mar 26, 2016, 4:08 PM UTC

mwcampbell wrote: post #52

How much of the poor performance discussed in this article is due to Chrome itself, and how much is due to the fact that Android devices tend to have worse single-core performance than iOS devices? Is there a browser for Android based on a recent version of WebKit (not Blink)? If so, that would help answer the question.

Post by zipwitch » Sat, Mar 26, 2016, 4:10 PM UTC

Razengan wrote: post #33

dsugarman wrote: post #9

I was waiting for someone to come out and say it. 6 months ago, I couldn't imagine using another browser regularly but chrome has become so slow for me, I can't stand it. I switched to Firefox.

Chrome was (probably still is) the only usable browser left on Windows, but I never used it or had to use it ever since I switched to Macs a few years ago. Aside from the plugins ecosystem (which I don't need) Safari works infinitely better (loads faster, uses less resources, even with 100s of tabs, and has nice little features like the Reading List, Reading Mode, Force-Touch Peek and so on) and fits into the OS X lo…