I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…
It still is behind technically isn't it? Does Firefox support Site Isolation yet?
We Need Chrome No More
71–80 of 536 posts
Re: We Need Chrome No More
#72Earlier quoted context omitted.
But as a web developer I don't necessarily care about standards. I want the page to work for as many users as possible. For the longest time this meant to support IE's way of doing things, now it means to support Chrome (unless you target Enterprise users). Even if you develop for Chrome, Firefox and Edge you'll just end up building workarounds for all 3, not adhering strictly to the standard.
Sorry to break this to you, but as a web developer you should only care about standards, otherwise you have no standards. The standards are a single source of truth for your production, if you build solely to a single browsers quirks (in this case Chrome) then those quirks can change at any time.
And then what?
Re: We Need Chrome No More
#73Re: We Need Chrome No More
#74I think the dominance of Webkit is concerning, but I don't think we can reuse the justifications of ten years ago to say why. Chrome continues to be technically strong (though perhaps not as much) and continues to push web standards (though perhaps too many supporting Google). The situation just isn't as bad today as it was. There is a lot less friction in the everyday experience of developers and users who want to use cutting-edge web standards.
Monoculture is bad, but it's hard to get people excited about challenging it when the monocultural product isn't awful.
Re: We Need Chrome No More
#75I find posts like this kind of interesting. Chrome gained prominence because it had great performance improvements over the competition -- IE and Firefox. IE in particular was dog slow at all times, and Chrome ran everything at least as well and almost always better. Firefox didn't have process isolation when Chrome came onto the scene, and that kind of knocked it for security and stability. It's not as if people swi…
>It's not as if people switched just because it had Google branding. Everyone switched because it was quantifiably better. The knowledgeable minority, maybe. _Most_ people switched because Google pushed it like a piece of adware. Bundling it with other software installers, prompting you to use it whenever you use Google search or other products, and bundling it with an OS.
Re: We Need Chrome No More
#76Other than AMP, I can't really think of a case that I would characterize as "Google abusing its position" w.r.t. Open Web. It was Chrome that led the push for PWAs, which I think is both great for the Open Web and consumers... The author complains about other vendors being "called laggards", which - let's be honest - we're really talking about how long Apple/Safari dragged their feet on Service Workers... and they _s…
Re: We Need Chrome No More
#77Do we know why Google grew dissatisfied with Apple and forked Webkit?
Do we know why Google grew dissatisfied with sites serving their own content and developed AMP?
Google making the web faster is a mutually beneficial arrangement.
Re: We Need Chrome No More
#78I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…
> Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. Curious, I remember speed being the primary reason. Google invented V8 (the javascript engine), with some pretty decent optimizations and a well-working JIT on i386/amd64 platforms. At the time when chromium came out, it handled some JS-heavy applications very nicely that Firefox struggled w…
(I suppose it makes sense I'd agree with someone else with a Perl-inspired handle :-)
Re: We Need Chrome No More
#79Extensions. I am now locked into Chrome because several services I use require Chrome extensions that aren't available elsewhere. The idea that Chrome can be unseated, or isn't needed, is unrealistic for the many users who rely on Chrome-exclusive extensions.
Re: We Need Chrome No More
#80I enjoyed this post, but I take issue with the idea that Chrome was initially adopted, or served, "to break the Web free from corporate greed." Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. No one else had this at the time, and it was a big deal because Flash was still widespread so sites were even less stable than they are today. Luckily…
> Chrome's appeal was primarily technical. Each tab got its own process and could crash without taking down the entire browser. Curious, I remember speed being the primary reason. Google invented V8 (the javascript engine), with some pretty decent optimizations and a well-working JIT on i386/amd64 platforms. At the time when chromium came out, it handled some JS-heavy applications very nicely that Firefox struggled w…
Obviously the v8 stuff also made a massive difference too.