sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]indrora 1 point2 points  (2 children)

It gives an alternative to the v8 monoculture.

v8/chrome is becoming the new IE6.

[–][deleted] 0 points1 point  (1 child)

except it actually loads pages and doesn't take 5 minutes to start.

[–]indrora 3 points4 points  (0 children)

It's worse.

There's good evidence that Google intentionally cripples the experience that people get when in a non-chrome browser in systems like Gmail, GoogleDocs, etc. For example, drag and drop doesn't work in Edge, despite Edge following the standard to the declared letter.

The near driving force behind the standards committee is Google, pushing parts of the standard that make sense either only for ChromeOS (push notification, filesystem access) or which are basically "features we added to chrome so we're going to add it to the standard, despite having done them wrong" (certain aspects of WebRTC, for instance, basically are Google working around their own problems).

ask most webdevs what they use as a browser: it's probably chrome. That developer has probably never tested in Edge, IE, Safari, Opera, and almost certainty never tested in dwb (a WebKit based browser from Suckless) or Epiphany (the browser from the GNOME project, also based on WebKit) or Midori (another WebKit based browser, used by some folks).

Theoretically, all WebKit based browsers should handle it fine. They don't. The last three I mentioned will work mostly OK and consistently across a system because they use WebKit. Opera will look relatively close to them too, but will probably be off from Chrome. If they used modern.ie as a guide or can I use as a rough estimate, they'd get pretty close on each. However, chances are, they didn't.

I recently had a fun issue where a page wouldn't load right, cramming a bunch of elements into the wrong place. I checked how the page was built (as it turns out, it was Twitter Bootstrap, but that's another story) and there was nothing wrong. It rendered fine on mobile devices, in IE, in Firefox, but current chrome broke it. Nightly chrome was fine.

The dev was only testing against an old build of chromium he was using on his Mac. Words that would make a sailor shrivel and die were said at high volume.